← previous blocknext block →recent activity
Analyzing
Block #85,645,393
15 transactions · 14 stateful · 2026-07-04 23:40:33 UTC
Parallelism
80/100
Blocked
21%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,645,393 · 15 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
1w07w18w213w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x21898044…a071
0x065c9d…c394
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0a14ed8e…d351
0x065c9d…c394
2 touches
0 conflicts
0x2b1d5637…e0b3
0x065c9d…c394
2 touches
0 conflicts
0xaefbc8e9…85c1
0x065c9d…c394
2 touches
0 conflicts
0xcc327642…0d55
0x065c9d…c394
2 touches
0 conflicts
0xe7a36890…e317
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity