← previous blocknext block →recent activity
Analyzing
Block #90,322,998
8 transactions · 8 stateful · 2026-07-25 22:39:14 UTC
Parallelism
63/100
Blocked
25%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,322,998 · 8 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
2w03w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x96c36734…b2e3
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x033cf007…136d
0x34b655…2a6f
4 touches
1 conflict
0x01c23f23…88f5
0x34b655…2a6f
2 touches
0 conflicts
0x0431e51f…6f91
0x34b655…2a6f
2 touches
0 conflicts
0x0aa5e418…5d1d
0x34b655…2a6f
2 touches
0 conflicts
0x0e22f39d…b92b
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 0x96c36734dd…62b2e3
Audit this contract →
← previous block·next block →recent activity