← previous blocknext block →recent activity
Analyzing
Block #85,803,541
11 transactions · 10 stateful · 2026-07-05 17:14:54 UTC
Parallelism
82/100
Blocked
10%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,803,541 · 11 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
1w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5937bb0b…263b
0x065c9d…c394
4 touches
1 conflict
0xd1fc86ed…01fe
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x1a801c2a…5fc6
0x065c9d…c394
3 touches
1 conflict
0x96a1909c…86f9
0x065c9d…c394
3 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x09500602…94e9
0x34b655…2a6f
2 touches
0 conflicts
0x09500602…94ea
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 0x5937bb0bbd…f3263b
Audit this contract →
← previous block·next block →recent activity