← previous blocknext block →recent activity
Analyzing
Block #85,125,456
18 transactions · 13 stateful · 2026-07-02 13:57:46 UTC
Parallelism
78/100
Blocked
38%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,125,456 · 18 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
1w02w18w09w110w211w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22d3c767…e4d1
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x1b3114cd…5e2d
0xa6afd3…d132
6 touches
3 conflicts
0x66c5e348…51d0
0xa6afd3…d132
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x656bd53e…af4e
0x34b655…2a6f
4 touches
1 conflict
0x73f16822…0338
0x34b655…2a6f
4 touches
1 conflict
0x7fcfe8d7…c1cd
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 0x22d3c767ef…68e4d1
Audit this contract →
← previous block·next block →recent activity