← previous blocknext block →recent activity
Analyzing
Block #86,245,902
17 transactions · 14 stateful · 2026-07-07 18:26:14 UTC
Parallelism
82/100
Blocked
14%
Avg conflicts / tx
0.24
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,245,902 · 17 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
2w04w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xcc4f1f14…aa5f
0x065c9d…c394
6 touches
3 conflicts
0xdfa159d0…1576
0x065c9d…c394
4 touches
1 conflict
0x1ae856ed…4506
0x065c9d…c394
4 touches
1 conflict
0xe8a217d7…87a6
0x065c9d…c394
3 touches
1 conflict
0x1ca99ffb…5576
0xd32edf…ff58
3 touches
1 conflict
0x79a88594…c8c3
0x065c9d…c394
3 touches
1 conflict
0x7c403af1…31b1
0x3bd359…433a
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