← previous blocknext block →recent activity
Analyzing
Block #90,651,307
14 transactions · 13 stateful · 2026-07-27 02:22:44 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,651,307 · 14 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
1w02w14w06w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfc3d5171…8357
0x34b655…2a6f
6 touches
3 conflicts
0x2e19029d…72a7
0x34b655…2a6f
4 touches
1 conflict
0x3ab53f27…f985
0x34b655…2a6f
4 touches
1 conflict
0x40cc4a3b…8707
0x34b655…2a6f
4 touches
1 conflict
0x41e94e96…81f6
0x34b655…2a6f
4 touches
1 conflict
0x4cb6b7e9…c8aa
0x34b655…2a6f
4 touches
1 conflict
0x70dd4412…e645
0x34b655…2a6f
4 touches
1 conflict
0x77844cf2…2d28
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
3 conflicts on slot 0xfc3d51716d…008357
Audit this contract →
← previous block·next block →recent activity