← previous blocknext block →recent activity
Analyzing
Block #85,568,729
64 transactions · 47 stateful · 2026-07-04 15:10:00 UTC
Parallelism
73/100
Blocked
72%
Avg conflicts / tx
2.7
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #85,568,729 · 64 txs across 17 waves · depth 17
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w08w19w210w312w413w515w616w718w843w944w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
26 touches
78 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
20 touches
45 conflicts
0xb0446875…2b96
0x34b655…2a6f
18 touches
36 conflicts
0x2c8bf7d9…3cc7
0xc8689a…ee79
18 touches
36 conflicts
0x45597879…8174
0x34b655…2a6f
16 touches
28 conflicts
0x202c03eb…cf33
0xa6afd3…d132
16 touches
28 conflicts
0xbfca3cd0…5023
0x34b655…2a6f
16 touches
28 conflicts
0x00000000…003d
0xa6afd3…d132
16 touches
28 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
78 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity