← previous blocknext block →recent activity
Analyzing
Block #85,971,178
17 transactions · 12 stateful · 2026-07-06 11:51:54 UTC
Parallelism
88/100
Blocked
8%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,971,178 · 17 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd366b710…f4ed
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x52e69143…95ad
0x065c9d…c394
4 touches
1 conflict
0x2bccac53…647f
0x065c9d…c394
2 touches
0 conflicts
0x9d6b0801…8124
0x065c9d…c394
2 touches
0 conflicts
0xb974ece0…deec
0x065c9d…c394
2 touches
0 conflicts
0xe09d7e46…16fd
0x065c9d…c394
2 touches
0 conflicts
0xe6e103fc…6759
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 0xd366b71020…e3f4ed
Audit this contract →
← previous block·next block →recent activity