← previous blocknext block →recent activity
Analyzing
Block #85,496,356
9 transactions · 9 stateful · 2026-07-04 07:08:17 UTC
Parallelism
78/100
Blocked
11%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,496,356 · 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
1w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc2e65068…e03a
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x93b8e3c0…3f81
0x065c9d…c394
3 touches
1 conflict
0xa1e8c719…5fd8
0x065c9d…c394
3 touches
1 conflict
0x11d00a0c…dd16
0x065c9d…c394
2 touches
0 conflicts
0xf302fb92…67a3
0x065c9d…c394
2 touches
0 conflicts
0xfdfe4427…e1ae
0x065c9d…c394
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
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 0xc2e65068fb…b3e03a
Audit this contract →
← previous block·next block →recent activity