← previous blocknext block →recent activity
Analyzing
Block #91,285,912
13 transactions · 12 stateful · 2026-07-29 07:37:08 UTC
Parallelism
69/100
Blocked
42%
Avg conflicts / tx
0.69
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,285,912 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w06w17w19w010w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xefcdf197…96a2
0x34b655…2a6f
4 touches
1 conflict
0xfb0022d6…1264
0x34b655…2a6f
4 touches
1 conflict
0xffb4e475…08b6
0x34b655…2a6f
4 touches
1 conflict
0x54f38877…65d4
0x34b655…2a6f
4 touches
1 conflict
0x66f7c9fa…39a3
0x34b655…2a6f
4 touches
1 conflict
0x6c7cb3c8…71da
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity