← previous blocknext block →recent activity
Analyzing
Block #85,140,416
29 transactions · 24 stateful · 2026-07-02 15:37:42 UTC
Parallelism
66/100
Blocked
58%
Avg conflicts / tx
1.38
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #85,140,416 · 29 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w08w09w110w211w312w413w514w615w717w126w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
16 touches
28 conflicts
0xaa48195d…ffee
0x34b655…2a6f
12 touches
15 conflicts
0x922c7ebd…6600
0xc8689a…ee79
12 touches
15 conflicts
0xa0efa7bc…8b24
0x34b655…2a6f
12 touches
15 conflicts
0xc99e7125…81b1
0x34b655…2a6f
10 touches
10 conflicts
0x7c0bdc54…9dde
0x34b655…2a6f
10 touches
10 conflicts
0xa1144aa9…7f67
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 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
28 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity