← previous blocknext block →recent activity
Analyzing
Block #85,767,300
11 transactions · 10 stateful · 2026-07-05 13:13:29 UTC
Parallelism
64/100
Blocked
30%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,767,300 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xb597db8a…193b
0x065c9d…c394
3 touches
1 conflict
0x64045eda…aa3a
0x065c9d…c394
3 touches
1 conflict
0x11c78067…0c03
0x065c9d…c394
2 touches
0 conflicts
0x12994734…fabf
0x065c9d…c394
2 touches
0 conflicts
0x168cdbd5…c239
0x065c9d…c394
2 touches
0 conflicts
0x34b1cb7c…2a78
0x065c9d…c394
2 touches
0 conflicts
0x76fae77a…e928
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity