← previous blocknext block →recent activity
Analyzing
Block #89,691,039
13 transactions · 13 stateful · 2026-07-23 17:29:05 UTC
Parallelism
69/100
Blocked
46%
Avg conflicts / tx
0.85
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,691,039 · 13 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
1w03w15w06w17w28w39w210w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x0a2fbf…29b1
8 touches
6 conflicts
0x0e64bc92…a888
0x0a2fbf…29b1
8 touches
6 conflicts
0x0e64bc92…a889
0x0a2fbf…29b1
8 touches
6 conflicts
0xe336c4a4…d689
0x0a2fbf…29b1
8 touches
6 conflicts
0xe336c4a4…d68a
0x0a2fbf…29b1
8 touches
6 conflicts
0xe336c4a4…d68d
0x0a2fbf…29b1
8 touches
6 conflicts
0x00000000…0005
0x370e2e…63b4
8 touches
6 conflicts
0x1bff683e…7ecb
0x754704…b603
8 touches
6 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: 0x0a2fbf2d…f729b1
6 conflicts on slot 0x0000000000…000006
Audit this contract →
← previous block·next block →recent activity