← previous blocknext block →recent activity
Analyzing
Block #89,281,341
13 transactions · 11 stateful · 2026-07-21 20:46:51 UTC
Parallelism
77/100
Blocked
18%
Avg conflicts / tx
0.15
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,281,341 · 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
1w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0eb5755c…51a2
0x34b655…2a6f
4 touches
1 conflict
0x7525206c…fbd5
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf3e0b949…771f
0x34b655…2a6f
4 touches
1 conflict
0x8b818135…eff8
0x34b655…2a6f
4 touches
1 conflict
0x6b436af2…3c05
0x34b655…2a6f
4 touches
1 conflict
0x4755fafb…859b
0x34b655…2a6f
2 touches
0 conflicts
0x5e0b8bbe…377b
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 0x0eb5755c90…4751a2
Audit this contract →
← previous block·next block →recent activity