← previous blocknext block →recent activity
Analyzing
Block #95,386,657
47 transactions · 42 stateful · 2026-08-12 15:57:08 UTC
Parallelism
62/100
Blocked
76%
Avg conflicts / tx
3
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #95,386,657 · 47 txs across 18 waves · depth 18
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w06w17w28w39w410w511w612w222w623w727w730w232w1133w336w541w1343w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4cabb80a…46bf
0x34b655…2a6f
18 touches
36 conflicts
0xec7d120d…7084
0x34b655…2a6f
14 touches
21 conflicts
0x4efae872…6aa8
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x43fd3667…094b
0x34b655…2a6f
10 touches
10 conflicts
0x66d5e476…8a1f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xfddc28be…e776
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
36 conflicts on slot 0x4cabb80a0e…7546bf
Audit this contract →
← previous block·next block →recent activity