← previous blocknext block →recent activity
Analyzing
Block #89,666,922
32 transactions · 31 stateful · 2026-07-23 15:26:42 UTC
Parallelism
56/100
Blocked
55%
Avg conflicts / tx
3.06
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #89,666,922 · 32 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w06w17w08w19w210w311w412w513w614w715w816w917w1018w1119w1220w1322w225w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x0a2fbf…29b1
28 touches
91 conflicts
0x00000000…0005
0x370e2e…63b4
28 touches
91 conflicts
0x1bff683e…7ecb
0x754704…b603
28 touches
91 conflicts
0x55b4e430…44cb
0x754704…b603
28 touches
91 conflicts
0x6a69751a…7205
0x0a2fbf…29b1
16 touches
28 conflicts
0x6a69751a…7208
0x0a2fbf…29b1
16 touches
28 conflicts
0x9390fdf2…f68c
0x0a2fbf…29b1
16 touches
28 conflicts
0x9390fdf2…f68d
0x0a2fbf…29b1
16 touches
28 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
91 conflicts on slot 0x0000000000…000006
Audit this contract →
← previous block·next block →recent activity