← previous blocknext block →recent activity
Analyzing
Block #85,677,323
9 transactions · 9 stateful · 2026-07-05 03:13:04 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,677,323 · 9 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w27w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x54b193ad…c830
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x176a55d6…4c8c
0x065c9d…c394
2 touches
0 conflicts
0x46171a9d…bf7f
0x065c9d…c394
2 touches
0 conflicts
0x73de51c4…3838
0x065c9d…c394
2 touches
0 conflicts
0x845a6ab5…ed62
0x065c9d…c394
2 touches
0 conflicts
0xa0b5be2b…64d2
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