← previous blocknext block →recent activity
Analyzing
Block #95,074,346
36 transactions · 32 stateful · 2026-08-11 13:33:45 UTC
Parallelism
64/100
Blocked
72%
Avg conflicts / tx
2.11
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #95,074,346 · 36 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w48w09w110w011w012w113w114w215w216w317w418w519w620w525w726w530w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64db
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x1c1a65d0…3fc1
0xd32edf…ff58
9 touches
10 conflicts
0x734ee320…caae
0x34b655…2a6f
8 touches
6 conflicts
0x08636046…e60f
0x34b655…2a6f
8 touches
6 conflicts
0x4cabb80a…46bf
0x34b655…2a6f
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xf9e23360…8ef7
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
21 conflicts on slot 0xb3fb9fb561…7664db
Audit this contract →
← previous block·next block →recent activity