← previous blocknext block →recent activity
Analyzing
Block #85,360,307
16 transactions · 13 stateful · 2026-07-03 16:02:14 UTC
Parallelism
88/100
Blocked
15%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,360,307 · 16 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
2w010w111w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x1c8a3a66…2a9c
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x3ad2a4a9…109c
0x065c9d…c394
2 touches
0 conflicts
0xa7ea76a3…b5c9
0x065c9d…c394
2 touches
0 conflicts
0xe2a82cac…12dd
0x065c9d…c394
2 touches
0 conflicts
0xf6a46c26…1a68
0x065c9d…c394
2 touches
0 conflicts
0xfa98f7c4…8da4
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity