← previous blocknext block →recent activity
Analyzing
Block #89,666,182
37 transactions · 32 stateful · 2026-07-23 15:22:56 UTC
Parallelism
68/100
Blocked
66%
Avg conflicts / tx
2.41
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #89,666,182 · 37 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w07w18w29w310w411w012w114w215w316w417w518w619w725w128w529w631w734w335w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x0a2fbf…29b1
24 touches
66 conflicts
0x00000000…0005
0x370e2e…63b4
24 touches
66 conflicts
0x1bff683e…7ecb
0x754704…b603
24 touches
66 conflicts
0x55b4e430…44cb
0x754704…b603
24 touches
66 conflicts
0x78c5d689…2337
0x0a2fbf…29b1
16 touches
28 conflicts
0xf75cb9d0…a6b3
0x0a2fbf…29b1
16 touches
28 conflicts
0xf75cb9d0…a6b4
0x0a2fbf…29b1
16 touches
28 conflicts
0xf75cb9d0…a6b7
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
66 conflicts on slot 0x0000000000…000006
Audit this contract →
← previous block·next block →recent activity