← previous blocknext block →recent activity
Analyzing
Block #86,446,080
55 transactions · 39 stateful · 2026-07-08 16:43:13 UTC
Parallelism
71/100
Blocked
62%
Avg conflicts / tx
1.89
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #86,446,080 · 55 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w28w011w112w213w314w015w126w027w128w229w330w431w532w633w734w835w936w1037w1144w147w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
26 touches
78 conflicts
0x3230277c…ef39
0xc8689a…ee79
12 touches
15 conflicts
0xd92a03c7…bfc7
0x34b655…2a6f
12 touches
15 conflicts
0x1d9867ad…6d9a
0x34b655…2a6f
12 touches
15 conflicts
0x38e70d73…f7e2
0x34b655…2a6f
12 touches
15 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x9cec634a…8adc
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 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