← previous blocknext block →recent activity
Analyzing
Block #89,689,972
25 transactions · 21 stateful · 2026-07-23 17:23:42 UTC
Parallelism
88/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,689,972 · 25 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
1w02w14w05w06w112w213w015w117w018w119w223w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x714a26…182d
6 touches
3 conflicts
0x00000000…0003
0x714a26…182d
6 touches
3 conflicts
0x4c770fe0…b972
0x3bd359…433a
6 touches
3 conflicts
0xddc22bc2…7f7a
0x754704…b603
6 touches
3 conflicts
0x392a02b5…0019
0x81a224…7777
6 touches
3 conflicts
0xd785526f…b286
0xd32edf…ff58
5 touches
3 conflicts
0xc824469a…641e
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
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: 0x714a2694…f2182d
3 conflicts on slot 0x0000000000…000000
Audit this contract →
← previous block·next block →recent activity