← previous blocknext block →recent activity
Analyzing
Block #90,610,236
9 transactions · 8 stateful · 2026-07-26 22:56:07 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,610,236 · 9 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x757b0543…e087
0x34b655…2a6f
4 touches
1 conflict
0xf302a4c7…c8e0
0x34b655…2a6f
4 touches
1 conflict
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x1896cf58…6b31
0x34b655…2a6f
2 touches
0 conflicts
0x3054b094…bab9
0x34b655…2a6f
2 touches
0 conflicts
0x3b1ce1dd…dc2f
0x34b655…2a6f
2 touches
0 conflicts
0x52f7c71c…d0a6
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 0x757b054398…dbe087
Audit this contract →
← previous block·next block →recent activity