← previous blocknext block →recent activity
Analyzing
Block #85,958,239
9 transactions · 7 stateful · 2026-07-06 10:25:37 UTC
Parallelism
78/100
Blocked
14%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,958,239 · 9 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xe52aba76…9c8b
0x065c9d…c394
4 touches
1 conflict
0xa4f80979…4d71
0x065c9d…c394
4 touches
1 conflict
0xd607916b…f445
0x065c9d…c394
3 touches
1 conflict
0xd8530bd6…b22f
0x065c9d…c394
3 touches
1 conflict
0xfa56a5bb…3253
0x065c9d…c394
3 touches
1 conflict
0xff0bf2f5…7dcb
0x065c9d…c394
3 touches
1 conflict
0x921a113e…6fb5
0x34b655…2a6f
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