← previous blocknext block →recent activity
Analyzing
Block #86,709,159
40 transactions · 33 stateful · 2026-07-09 22:03:51 UTC
Parallelism
63/100
Blocked
76%
Avg conflicts / tx
2.23
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #86,709,159 · 40 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w26w39w010w111w212w313w414w516w517w618w319w220w722w323w425w426w427w533w934w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70ff9262…8d80
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xfaef08b1…0696
0x34b655…2a6f
12 touches
15 conflicts
0xa7013be2…c0a8
0x34b655…2a6f
10 touches
10 conflicts
0x8e8f0055…5527
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0xa08f40b2…9a93
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
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
21 conflicts on slot 0x70ff92623d…f38d80
Audit this contract →
← previous block·next block →recent activity