← previous blocknext block →recent activity
Analyzing
Block #95,075,061
51 transactions · 46 stateful · 2026-08-11 13:37:21 UTC
Parallelism
74/100
Blocked
72%
Avg conflicts / tx
2.24
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #95,075,061 · 51 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
1w02w13w24w37w08w212w413w514w616w717w830w139w940w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4cabb80a…46bf
0x34b655…2a6f
14 touches
21 conflicts
0x889d5e90…929a
0x2a68ba…90c5
12 touches
15 conflicts
0xec7d120d…7084
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
10 touches
10 conflicts
0xc56ce108…830e
0xd32edf…ff58
9 touches
10 conflicts
0xac3e4969…39e9
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0xeae24c…0be0
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
21 conflicts on slot 0x4cabb80a0e…7546bf
Audit this contract →
← previous block·next block →recent activity