← previous blocknext block →recent activity
Analyzing
Block #85,967,926
12 transactions · 11 stateful · 2026-07-06 11:30:14 UTC
Parallelism
83/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,967,926 · 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
0xa4f80979…4d71
0x065c9d…c394
4 touches
1 conflict
0xba62c547…57a1
0x065c9d…c394
4 touches
1 conflict
0xd71e4ea3…3fbc
0x065c9d…c394
3 touches
1 conflict
0x65515170…d6d0
0x065c9d…c394
3 touches
1 conflict
0x440c2c2e…053d
0x065c9d…c394
3 touches
1 conflict
0x54f8b53b…2993
0x065c9d…c394
2 touches
0 conflicts
0x5736e5b2…4080
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