← previous blocknext block →recent activity
Analyzing
Block #89,854,001
6 transactions · 6 stateful · 2026-07-24 07:11:29 UTC
Parallelism
67/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,854,001 · 6 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd9cf1be5…305d
0x34b655…2a6f
4 touches
1 conflict
0x081eb1d8…4caf
0x34b655…2a6f
4 touches
1 conflict
0x2c2761c0…476e
0x34b655…2a6f
4 touches
1 conflict
0x35ef736d…58fd
0x34b655…2a6f
4 touches
1 conflict
0x8ff85b19…dde0
0x34b655…2a6f
4 touches
1 conflict
0x9ce1d97b…4b2d
0x34b655…2a6f
4 touches
1 conflict
0xaa3f4e62…c8f7
0x34b655…2a6f
4 touches
1 conflict
0xb8e2871c…11b9
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 0xd9cf1be5c8…5b305d
Audit this contract →
← previous block·next block →recent activity