← previous blocknext block →recent activity
Analyzing
Block #89,403,862
14 transactions · 11 stateful · 2026-07-22 10:25:51 UTC
Parallelism
79/100
Blocked
27%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,403,862 · 14 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
5w06w18w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x34933aba…06e4
0x34b655…2a6f
6 touches
3 conflicts
0xe561281f…7569
0x34b655…2a6f
6 touches
3 conflicts
0x37ee30c9…9e70
0x34b655…2a6f
6 touches
3 conflicts
0x5e2a007d…30a7
0x34b655…2a6f
5 touches
3 conflicts
0xfa4abfe1…582c
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x0bcff46d…ec22
0x34b655…2a6f
4 touches
1 conflict
0x3733588d…c162
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 0x34933aba00…e806e4
Audit this contract →
← previous block·next block →recent activity