← previous blocknext block →recent activity
Analyzing
Block #86,447,637
72 transactions · 50 stateful · 2026-07-08 16:53:38 UTC
Parallelism
71/100
Blocked
68%
Avg conflicts / tx
2.35
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #86,447,637 · 72 txs across 21 waves · depth 21
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w614w217w347w751w853w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
24 touches
66 conflicts
0xbf95e030…94b1
0xd32edf…ff58
17 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xb624d2ea…8c87
0x34b655…2a6f
14 touches
21 conflicts
0x6be79ced…ccac
0x34b655…2a6f
10 touches
10 conflicts
0x9ad325f5…cc43
0x34b655…2a6f
10 touches
10 conflicts
0x9cec634a…8adc
0x34b655…2a6f
10 touches
10 conflicts
0x2c8bf7d9…3cc7
0xc8689a…ee79
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
66 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity