← previous blocknext block →recent activity
Analyzing
Block #101,984,813
18 transactions · 18 stateful · 2026-09-04 19:34:51 UTC
Parallelism
61/100
Blocked
50%
Avg conflicts / tx
1.39
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #101,984,813 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w17w211w012w115w416w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
14 touches
21 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
12 touches
15 conflicts
0xf7772b49…fc12
0x34b655…2a6f
6 touches
3 conflicts
0x29a58269…011a
0x34b655…2a6f
6 touches
3 conflicts
0x6823c28e…594c
0x34b655…2a6f
6 touches
3 conflicts
0x7dd96c96…7335
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0xa1a01ded…c087
0x34b655…2a6f
6 touches
3 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
21 conflicts on slot 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity