← previous blocknext block →recent activity
Analyzing
Block #85,352,423
20 transactions · 16 stateful · 2026-07-03 15:09:46 UTC
Parallelism
85/100
Blocked
38%
Avg conflicts / tx
0.35
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,352,423 · 20 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
1w02w15w06w07w18w213w114w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x05edf2cf…ac3c
0x34b655…2a6f
4 touches
1 conflict
0x1da60af2…3010
0x34b655…2a6f
4 touches
1 conflict
0x37258f28…4359
0x34b655…2a6f
4 touches
1 conflict
0x37534430…c68b
0x34b655…2a6f
4 touches
1 conflict
0x663d3288…f460
0x34b655…2a6f
4 touches
1 conflict
0x8eb0ac6b…a73a
0x34b655…2a6f
4 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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity