← previous blocknext block →recent activity
Analyzing
Block #85,515,335
9 transactions · 6 stateful · 2026-07-04 09:14:29 UTC
Parallelism
78/100
Blocked
17%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,515,335 · 9 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
3w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64dc
0x34b655…2a6f
4 touches
1 conflict
0x7b3a71df…68d7
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x18ad7082…fec5
0x065c9d…c394
2 touches
0 conflicts
0x3bc4f628…a0a9
0x065c9d…c394
2 touches
0 conflicts
0x8e3535bd…e1b7
0x065c9d…c394
2 touches
0 conflicts
0xaa36e5c5…fa64
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: Perpl
1 conflict on slot 0xb3fb9fb561…7664db
Audit this contract →
← previous block·next block →recent activity