← previous blocknext block →recent activity
Analyzing
Block #90,231,339
18 transactions · 18 stateful · 2026-07-25 14:55:10 UTC
Parallelism
56/100
Blocked
56%
Avg conflicts / tx
1.83
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #90,231,339 · 18 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w07w18w29w310w411w512w613w715w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x0a2fbf…29b1
16 touches
28 conflicts
0xbea313f5…cb2c
0x0a2fbf…29b1
16 touches
28 conflicts
0xbea313f5…cb2d
0x0a2fbf…29b1
16 touches
28 conflicts
0xbea313f5…cb2e
0x0a2fbf…29b1
16 touches
28 conflicts
0xe39262f3…ed5d
0x0a2fbf…29b1
16 touches
28 conflicts
0xe39262f3…ed5e
0x0a2fbf…29b1
16 touches
28 conflicts
0xe39262f3…ed61
0x0a2fbf…29b1
16 touches
28 conflicts
0xe39262f3…ed63
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
28 conflicts on slot 0x0000000000…000006
Audit this contract →
← previous block·next block →recent activity