← previous blocknext block →recent activity
Analyzing
Block #87,629,382
17 transactions · 12 stateful · 2026-07-14 04:36:59 UTC
Parallelism
76/100
Blocked
42%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,629,382 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w17w08w19w210w311w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x0a2fbf…29b1
8 touches
6 conflicts
0x1d9c7a0c…244b
0x0a2fbf…29b1
8 touches
6 conflicts
0x1d9c7a0c…244c
0x0a2fbf…29b1
8 touches
6 conflicts
0x6c531230…70fc
0x0a2fbf…29b1
8 touches
6 conflicts
0x6c531230…70fd
0x0a2fbf…29b1
8 touches
6 conflicts
0x6c531230…7100
0x0a2fbf…29b1
8 touches
6 conflicts
0x00000000…0005
0x370e2e…63b4
8 touches
6 conflicts
0xb1c500c1…3b8d
0x370e2e…63b4
8 touches
6 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
6 conflicts on slot 0x0000000000…000006
Audit this contract →
← previous block·next block →recent activity