← previous blocknext block →recent activity
Analyzing
Block #85,409,892
22 transactions · 19 stateful · 2026-07-03 21:32:31 UTC
Parallelism
73/100
Blocked
42%
Avg conflicts / tx
0.86
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,409,892 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w210w011w112w213w314w215w016w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x830b63a6…8105
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xafb2524a…0ce4
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xfa928a78…c7be
0x34b655…2a6f
6 touches
3 conflicts
0x80398c66…f3cc
0x34b655…2a6f
4 touches
1 conflict
0x08e8f2c9…a11a
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
6 conflicts on slot 0x830b63a692…148105
Audit this contract →
← previous block·next block →recent activity