← previous blocknext block →recent activity
Analyzing
Block #85,137,840
24 transactions · 17 stateful · 2026-07-02 15:20:30 UTC
Parallelism
79/100
Blocked
47%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,137,840 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w06w113w014w115w216w318w119w220w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x268e7ce3…11b3
0x34b655…2a6f
6 touches
3 conflicts
0x2b638230…1832
0x34b655…2a6f
6 touches
3 conflicts
0x478f4afc…adff
0x34b655…2a6f
6 touches
3 conflicts
0x7523ad90…2ba5
0x34b655…2a6f
6 touches
3 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
6 touches
3 conflicts
0x9eb155db…f714
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity