← previous blocknext block →recent activity
Analyzing
Block #87,611,240
16 transactions · 14 stateful · 2026-07-14 02:35:39 UTC
Parallelism
81/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,611,240 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w08w19w210w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xefb6ea67…c412
0x34b655…2a6f
4 touches
1 conflict
0xb568bd0a…0a73
0x34b655…2a6f
4 touches
1 conflict
0xc2f84a16…86b8
0x34b655…2a6f
4 touches
1 conflict
0xcf504b9b…8df2
0x34b655…2a6f
4 touches
1 conflict
0xd64c1971…1bf2
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x212c5b04…5f01
0x34b655…2a6f
4 touches
1 conflict
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: Kuru Exchange: Market-MON/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity