← previous blocknext block →recent activity
Analyzing
Block #86,633,563
46 transactions · 35 stateful · 2026-07-09 13:37:57 UTC
Parallelism
59/100
Blocked
80%
Avg conflicts / tx
3.24
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #86,633,563 · 46 txs across 19 waves · depth 19
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w29w010w111w214w015w116w217w318w419w520w621w722w823w924w1025w1130w233w334w335w436w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
28 touches
91 conflicts
0x1941b441…5889
0x34b655…2a6f
12 touches
15 conflicts
0xd6d040d9…9ae3
0x34b655…2a6f
12 touches
15 conflicts
0xcd81cc7b…8da0
0x34b655…2a6f
10 touches
10 conflicts
0x199698ab…5768
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x40c49f…2af0
10 touches
10 conflicts
0x68e52406…3352
0x34b655…2a6f
9 touches
10 conflicts
0xca2926e0…61b5
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
91 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity