← previous blocknext block →recent activity
Analyzing
Block #86,239,416
19 transactions · 15 stateful · 2026-07-07 17:42:51 UTC
Parallelism
79/100
Blocked
20%
Avg conflicts / tx
0.21
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,239,416 · 19 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
1w013w114w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x92d610a6…9a40
0x2a68ba…90c5
4 touches
1 conflict
0xcc4f1f14…aa5f
0x065c9d…c394
4 touches
1 conflict
0xb1f6b574…aded
0x065c9d…c394
3 touches
1 conflict
0x40eada08…234b
0x0a4fcb…a602
2 touches
0 conflicts
0x12530975…a089
0x3bd359…433a
2 touches
0 conflicts
0x776b206d…6cf9
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0000
0x453805…c7fd
2 touches
0 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: Kuru Exchange: Market-MON/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity