← previous blocknext block →recent activity
Analyzing
Block #86,844,133
45 transactions · 41 stateful · 2026-07-10 13:05:51 UTC
Parallelism
64/100
Blocked
76%
Avg conflicts / tx
3.16
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #86,844,133 · 45 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
1w02w13w04w15w26w310w011w112w213w314w415w516w617w718w819w923w224w327w229w430w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
20 touches
45 conflicts
0xac2a0273…721b
0x34b655…2a6f
16 touches
28 conflicts
0xec7fe04a…3c56
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x737acb78…fce8
0x34b655…2a6f
12 touches
15 conflicts
0x7babfe9a…ff96
0x34b655…2a6f
10 touches
10 conflicts
0xa6ca03ef…80e4
0x34b655…2a6f
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
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
45 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity