← previous blocknext block →recent activity
Analyzing
Block #85,633,959
15 transactions · 10 stateful · 2026-07-04 22:24:20 UTC
Parallelism
87/100
Blocked
20%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,633,959 · 15 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
2w04w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2fb80aae…a042
0x34b655…2a6f
4 touches
1 conflict
0x7012e9c1…f525
0x34b655…2a6f
4 touches
1 conflict
0xc0eb79d1…29a4
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xeddb39cd…d209
0x34b655…2a6f
4 touches
1 conflict
0x985d02c5…3f13
0x065c9d…c394
2 touches
0 conflicts
0x9ff176a9…152e
0x065c9d…c394
2 touches
0 conflicts
0xfdd29ed8…d0bf
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 0x2fb80aaea3…c6a042
Audit this contract →
← previous block·next block →recent activity