← previous blocknext block →recent activity
Analyzing
Block #86,181,153
12 transactions · 10 stateful · 2026-07-07 11:13:45 UTC
Parallelism
83/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,181,153 · 12 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
1w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x18cf3003…51d1
0x065c9d…c394
4 touches
1 conflict
0x3e1274be…6391
0x065c9d…c394
2 touches
0 conflicts
0x71929658…70d8
0x065c9d…c394
2 touches
0 conflicts
0x85a972c7…f4d5
0x065c9d…c394
2 touches
0 conflicts
0xab3ff4a4…99eb
0x065c9d…c394
2 touches
0 conflicts
0xaf3fc3fb…05f3
0x065c9d…c394
2 touches
0 conflicts
0xcafa23ae…33fe
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity