← previous blocknext block →recent activity
Analyzing
Block #85,134,890
16 transactions · 14 stateful · 2026-07-02 15:00:49 UTC
Parallelism
88/100
Blocked
21%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,134,890 · 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
1w02w03w04w17w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xed1c1e70…a254
0x065c9d…c394
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x1b5d2e60…99b5
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x7ab9d0a7…fb9a
0x065c9d…c394
4 touches
1 conflict
0x780fcc11…4bab
0xd32edf…ff58
3 touches
1 conflict
0xdb4c9fa4…f435
0x065c9d…c394
2 touches
0 conflicts
0xf8a15bcb…3a89
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 0xed1c1e70d2…b6a254
Audit this contract →
← previous block·next block →recent activity