← previous blocknext block →recent activity
Analyzing
Block #86,355,457
14 transactions · 14 stateful · 2026-07-08 06:37:44 UTC
Parallelism
71/100
Blocked
21%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,355,457 · 14 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
1w02w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x148dc457…e120
0x065c9d…c394
2 touches
0 conflicts
0x3aa2ee9b…8c34
0x065c9d…c394
2 touches
0 conflicts
0x58c52474…6f97
0x065c9d…c394
2 touches
0 conflicts
0x8f242216…4bf7
0x065c9d…c394
2 touches
0 conflicts
0xbf6fb786…2940
0x065c9d…c394
2 touches
0 conflicts
0xd6b9120a…4b68
0x065c9d…c394
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