← previous blocknext block →recent activity
Analyzing
Block #87,911,298
19 transactions · 17 stateful · 2026-07-15 12:02:40 UTC
Parallelism
58/100
Blocked
59%
Avg conflicts / tx
1.74
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,911,298 · 19 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
4w05w16w27w08w19w210w311w412w513w614w716w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x0a2fbf…29b1
16 touches
28 conflicts
0xeef582b8…6038
0x0a2fbf…29b1
16 touches
28 conflicts
0xeef582b8…6039
0x0a2fbf…29b1
16 touches
28 conflicts
0xeef582b8…603c
0x0a2fbf…29b1
16 touches
28 conflicts
0x00000000…0005
0x370e2e…63b4
16 touches
28 conflicts
0x1bff683e…7ecb
0x754704…b603
16 touches
28 conflicts
0x55b4e430…44cb
0x754704…b603
16 touches
28 conflicts
0x678a0578…750e
0x0a2fbf…29b1
15 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