← previous blocknext block →recent activity
Analyzing
Block #86,362,986
16 transactions · 15 stateful · 2026-07-08 07:27:58 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,362,986 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w010w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd9a31d8a…d3cb
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x2ba090ba…1d58
0x065c9d…c394
3 touches
1 conflict
0x3be41b3c…23e6
0x065c9d…c394
3 touches
1 conflict
0x49cbdb1b…bda4
0x065c9d…c394
2 touches
0 conflicts
0x4e4ac93b…9613
0x065c9d…c394
2 touches
0 conflicts
0x685bc3d0…c7c3
0x065c9d…c394
2 touches
0 conflicts
0x7aa2dc6a…dab9
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
1 conflict on slot 0xd9a31d8ab3…d3d3cb
Audit this contract →
← previous block·next block →recent activity