← previous blocknext block →recent activity
Analyzing
Block #89,881,020
9 transactions · 8 stateful · 2026-07-24 09:27:24 UTC
Parallelism
56/100
Blocked
38%
Avg conflicts / tx
0.78
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,881,020 · 9 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
1w02w03w15w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17888f8a…bdb7
0x34b655…2a6f
6 touches
3 conflicts
0xeee60778…2df8
0x34b655…2a6f
6 touches
3 conflicts
0xf63c2a2b…bc5f
0x34b655…2a6f
6 touches
3 conflicts
0xf63c2a2b…bc60
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x8326b13b…bac0
0x34b655…2a6f
4 touches
1 conflict
0x83f3d320…fb59
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f0
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 0x17888f8add…5cbdb7
Audit this contract →
← previous block·next block →recent activity