← previous blocknext block →recent activity
Analyzing
Block #89,702,442
13 transactions · 8 stateful · 2026-07-23 18:26:33 UTC
Parallelism
77/100
Blocked
38%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,702,442 · 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
2w07w110w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x50c16ec6…4f00
0x34b655…2a6f
4 touches
1 conflict
0x1507536e…933f
0x34b655…2a6f
4 touches
1 conflict
0xe9ef16e7…2d22
0x34b655…2a6f
4 touches
1 conflict
0xc948dbdc…199a
0x34b655…2a6f
4 touches
1 conflict
0xd29e547b…a1dd
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x7fb99184…e8bb
0x34b655…2a6f
2 touches
0 conflicts
0xbcbf5d09…8bac
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 0x50c16ec606…d74f00
Audit this contract →
← previous block·next block →recent activity