← previous blocknext block →recent activity
Analyzing
Block #89,674,912
18 transactions · 14 stateful · 2026-07-23 16:07:34 UTC
Parallelism
78/100
Blocked
29%
Avg conflicts / tx
0.28
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,674,912 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w18w215w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x734ee320…caae
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xecf5834b…70b8
0x34b655…2a6f
4 touches
1 conflict
0xf77a2986…931c
0x34b655…2a6f
4 touches
1 conflict
0x0a57a2b8…3cdd
0x34b655…2a6f
4 touches
1 conflict
0x02d895f0…2b93
0x34b655…2a6f
4 touches
1 conflict
0x472e66d6…7003
0x34b655…2a6f
4 touches
1 conflict
0x4deeee1b…8c0c
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
3 conflicts on slot 0x734ee32053…cecaae
Audit this contract →
← previous block·next block →recent activity