← previous blocknext block →recent activity
Analyzing
Block #89,826,094
13 transactions · 11 stateful · 2026-07-24 04:50:45 UTC
Parallelism
77/100
Blocked
27%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,826,094 · 13 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
1w02w16w08w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8eed7e30…c1ef
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xa93224c6…ced4
0x34b655…2a6f
4 touches
1 conflict
0xa93224c6…ced5
0x34b655…2a6f
4 touches
1 conflict
0xe60e9000…c058
0x34b655…2a6f
4 touches
1 conflict
0xe751731d…9aa5
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x22e0cc1d…ad0d
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
1 conflict on slot 0x8eed7e30df…96c1ef
Audit this contract →
← previous block·next block →recent activity