← previous blocknext block →recent activity
Analyzing
Block #91,972,203
10 transactions · 9 stateful · 2026-07-31 17:11:07 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,972,203 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc9f4535e…4e1d
0x34b655…2a6f
4 touches
1 conflict
0x856d2776…04c9
0x34b655…2a6f
4 touches
1 conflict
0xbc96083d…124d
0x34b655…2a6f
4 touches
1 conflict
0x1ea0a6bc…6a74
0x2a68ba…90c5
2 touches
0 conflicts
0x0fffbee5…8e4f
0x34b655…2a6f
2 touches
0 conflicts
0x117e581f…7b67
0x34b655…2a6f
2 touches
0 conflicts
0x2210c4e2…2ea9
0x34b655…2a6f
2 touches
0 conflicts
0x25ecf913…0ad8
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xc9f4535ec0…8f4e1d
Audit this contract →
← previous block·next block →recent activity