← previous blocknext block →recent activity
Analyzing
Block #89,838,520
11 transactions · 10 stateful · 2026-07-24 05:53:31 UTC
Parallelism
82/100
Blocked
20%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,838,520 · 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
2w06w17w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3f5831e5…02b2
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd2df6160…cf1b
0x34b655…2a6f
4 touches
1 conflict
0xb1b21ea8…d790
0x34b655…2a6f
4 touches
1 conflict
0x4ab0fef9…caef
0x34b655…2a6f
2 touches
0 conflicts
0x5eb187dd…b1d6
0x34b655…2a6f
2 touches
0 conflicts
0x6d11d4a8…3a2d
0x34b655…2a6f
2 touches
0 conflicts
0x79e8f935…c3b6
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 0x3f5831e5e5…ee02b2
Audit this contract →
← previous block·next block →recent activity