← previous blocknext block →recent activity
Analyzing
Block #85,966,748
17 transactions · 15 stateful · 2026-07-06 11:22:26 UTC
Parallelism
88/100
Blocked
7%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,966,748 · 17 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
1w04w07w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x01b8ae7e…3643
0x065c9d…c394
4 touches
1 conflict
0xef3a3293…8f66
0x065c9d…c394
3 touches
1 conflict
0x9ce15a34…4de7
0x065c9d…c394
3 touches
1 conflict
0xdb50497a…b79c
0x065c9d…c394
3 touches
1 conflict
0x8a962816…5aaf
0xd32edf…ff58
3 touches
1 conflict
0x2d72b734…2836
0x188d58…ea8e
2 touches
0 conflicts
0x4dd1db39…a994
0x188d58…ea8e
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