← previous blocknext block →recent activity
Analyzing
Block #91,542,900
10 transactions · 9 stateful · 2026-07-30 05:11:29 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,542,900 · 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa9d7cd60…1ef3
0x34b655…2a6f
4 touches
1 conflict
0x033cf007…136d
0x34b655…2a6f
4 touches
1 conflict
0x33a24f73…b23a
0x34b655…2a6f
4 touches
1 conflict
0x21f49676…6f7e
0x34b655…2a6f
2 touches
0 conflicts
0x2d6538f7…afbe
0x34b655…2a6f
2 touches
0 conflicts
0x4e412b57…4771
0x34b655…2a6f
2 touches
0 conflicts
0x50fd6f6f…2048
0x34b655…2a6f
2 touches
0 conflicts
0x58940b94…acb3
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 0xa9d7cd6004…521ef3
Audit this contract →
← previous block·next block →recent activity