← previous blocknext block →recent activity
Analyzing
Block #86,563,273
65 transactions · 48 stateful · 2026-07-09 05:47:06 UTC
Parallelism
63/100
Blocked
75%
Avg conflicts / tx
2.83
Longest chain
24 deep
Execution timeline
did this block parallelize well?
view
block #86,563,273 · 65 txs across 24 waves · depth 24
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
wave w19
wave w20
wave w21
wave w22
wave w23
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w06w17w29w310w411w513w614w745w648w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
26 touches
78 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0x30dc4fdc…ec33
0xd32edf…ff58
15 touches
28 conflicts
0x8eb0ac6b…a73a
0x34b655…2a6f
12 touches
15 conflicts
0xa08f40b2…9a93
0x34b655…2a6f
12 touches
15 conflicts
0xdb3937e8…23cb
0x34b655…2a6f
10 touches
10 conflicts
0x1e48811e…2e39
0x34b655…2a6f
10 touches
10 conflicts
0x895303cc…6f57
0x34b655…2a6f
10 touches
10 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