← previous blocknext block →recent activity
Analyzing
Block #90,484,600
11 transactions · 9 stateful · 2026-07-26 12:24:09 UTC
Parallelism
82/100
Blocked
11%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,484,600 · 11 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
1w06w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5a4d5f09…5094
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x1a625412…648b
0x34b655…2a6f
2 touches
0 conflicts
0x1bc07c63…d6ad
0x34b655…2a6f
2 touches
0 conflicts
0x53355553…2976
0x34b655…2a6f
2 touches
0 conflicts
0x6767539b…f211
0x34b655…2a6f
2 touches
0 conflicts
0x6d11d4a8…3a2d
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 0x5a4d5f0922…aa5094
Audit this contract →
← previous block·next block →recent activity