← previous blocknext block →recent activity
Analyzing
Block #86,626,414
22 transactions · 18 stateful · 2026-07-09 12:50:08 UTC
Parallelism
77/100
Blocked
39%
Avg conflicts / tx
0.36
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,626,414 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w17w08w110w216w217w320w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x547f1bec…4423
0x34b655…2a6f
4 touches
1 conflict
0x8d0e98f3…7ba0
0x34b655…2a6f
4 touches
1 conflict
0x94ba9c4a…41d8
0x34b655…2a6f
4 touches
1 conflict
0xa3e06ffb…6c2b
0x34b655…2a6f
4 touches
1 conflict
0xb83387da…d672
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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