← previous blocknext block →recent activity
Analyzing
Block #89,538,344
13 transactions · 11 stateful · 2026-07-23 01:24:15 UTC
Parallelism
85/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,538,344 · 13 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
0xf4c9a0df…dcd4
0x34b655…2a6f
4 touches
1 conflict
0xdfe0a6d9…8bed
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x0c15f714…46ab
0x34b655…2a6f
2 touches
0 conflicts
0x0ca2f876…e241
0x34b655…2a6f
2 touches
0 conflicts
0x14398ebc…14d6
0x34b655…2a6f
2 touches
0 conflicts
0x14edac2b…36a6
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 0xf4c9a0dfc5…fcdcd4
Audit this contract →
← previous block·next block →recent activity