← previous blocknext block →recent activity
Analyzing
Block #85,758,284
9 transactions · 8 stateful · 2026-07-05 12:13:31 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,758,284 · 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
2w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x57182918…dd1d
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xb6fefaad…d88d
0x065c9d…c394
3 touches
1 conflict
0x6f999af5…bf4a
0x065c9d…c394
3 touches
1 conflict
0x04fb1393…d61e
0x065c9d…c394
2 touches
0 conflicts
0x2886e2bc…6ab8
0x065c9d…c394
2 touches
0 conflicts
0x3581a113…3ee1
0x065c9d…c394
2 touches
0 conflicts
0x54b7ad3c…f072
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 0x571829180a…efdd1d
Audit this contract →
← previous block·next block →recent activity