← previous blocknext block →recent activity
Analyzing
Block #85,630,296
16 transactions · 15 stateful · 2026-07-04 22:00:02 UTC
Parallelism
75/100
Blocked
47%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,630,296 · 16 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
0w02w03w04w15w28w311w112w113w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5fe7e126…6dd2
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x9ff176a9…152e
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
4 touches
1 conflict
0x5540f956…69e8
0x065c9d…c394
4 touches
1 conflict
0x2d79ed03…5164
0xd32edf…ff58
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
3 touches
1 conflict
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: Perpl
3 conflicts on slot 0x5fe7e1267e…896dd2
Audit this contract →
← previous block·next block →recent activity