← previous blocknext block →recent activity
Analyzing
Block #88,041,227
28 transactions · 26 stateful · 2026-07-16 02:31:43 UTC
Parallelism
43/100
Blocked
77%
Avg conflicts / tx
4.5
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #88,041,227 · 28 txs across 16 waves · depth 16
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
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w18w29w310w411w512w613w714w815w916w1017w1118w1219w1320w1421w1522w223w225w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x0a2fbf…29b1
32 touches
120 conflicts
0x4dc1f0b8…b834
0x0a2fbf…29b1
32 touches
120 conflicts
0x4dc1f0b8…b835
0x0a2fbf…29b1
32 touches
120 conflicts
0x4dc1f0b8…b838
0x0a2fbf…29b1
32 touches
120 conflicts
0x81273019…84cd
0x0a2fbf…29b1
32 touches
120 conflicts
0x81273019…84ce
0x0a2fbf…29b1
32 touches
120 conflicts
0x00000000…0005
0x370e2e…63b4
32 touches
120 conflicts
0x1bff683e…7ecb
0x754704…b603
32 touches
120 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
120 conflicts on slot 0x0000000000…000006
Audit this contract →
← previous block·next block →recent activity