← previous blocknext block →recent activity
Analyzing
Block #85,712,217
10 transactions · 8 stateful · 2026-07-05 07:06:54 UTC
Parallelism
80/100
Blocked
25%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,712,217 · 10 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
1w05w06w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x86e5693a…f140
0x065c9d…c394
4 touches
1 conflict
0x9a3068dd…18f0
0x34b655…2a6f
4 touches
1 conflict
0xbf140d9d…4923
0x34b655…2a6f
4 touches
1 conflict
0x9e9c86c2…7249
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x85fd6c70…a949
0x065c9d…c394
3 touches
1 conflict
0x9e4841a7…a333
0x065c9d…c394
3 touches
1 conflict
0x6bbfd96f…9048
0x065c9d…c394
3 touches
1 conflict
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 0x86e5693a2c…27f140
Audit this contract →
← previous block·next block →recent activity