← previous blocknext block →recent activity
Analyzing
Block #89,414,313
15 transactions · 12 stateful · 2026-07-22 11:35:42 UTC
Parallelism
80/100
Blocked
42%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,414,313 · 15 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
2w03w16w07w19w213w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6ad9e91…6025
0x34b655…2a6f
6 touches
3 conflicts
0x63da8263…7a24
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
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 0xc6ad9e91ae…016025
Audit this contract →
← previous block·next block →recent activity