← previous blocknext block →recent activity
Analyzing
Block #86,443,754
54 transactions · 41 stateful · 2026-07-08 16:27:39 UTC
Parallelism
80/100
Blocked
63%
Avg conflicts / tx
1.63
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #86,443,754 · 54 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w27w38w09w112w113w215w416w529w540w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
16 touches
28 conflicts
0x0c950793…899a
0xd32edf…ff58
13 touches
21 conflicts
0xac2a0273…721b
0x34b655…2a6f
12 touches
15 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
10 touches
10 conflicts
0xef65bff3…7c9d
0x2a68ba…90c5
10 touches
10 conflicts
0xc68d6f14…bdde
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x8a751d7a…247c
0xa6afd3…d132
8 touches
9 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
28 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity