← previous blocknext block →recent activity
Analyzing
Block #86,971,621
64 transactions · 40 stateful · 2026-07-11 03:18:02 UTC
Parallelism
70/100
Blocked
78%
Avg conflicts / tx
3.27
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #86,971,621 · 64 txs across 19 waves · depth 19
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
wave w17
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w011w112w213w314w416w021w122w223w324w444w147w448w555w656w657w558w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
38 touches
171 conflicts
0x0682a731…d1e7
0x34b655…2a6f
16 touches
28 conflicts
0x5f72d58f…c445
0x34b655…2a6f
16 touches
28 conflicts
0x64a785e4…0110
0x34b655…2a6f
16 touches
28 conflicts
0xfcdb5918…2b49
0x34b655…2a6f
16 touches
28 conflicts
0xd1ec0dfd…ccc0
0xc8689a…ee79
16 touches
28 conflicts
0x9e3f5c49…42e1
0x34b655…2a6f
16 touches
28 conflicts
0xafe3acc8…5c1c
0x34b655…2a6f
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
171 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity