← previous blocknext block →recent activity
Analyzing
Block #95,746,413
98 transactions · 63 stateful · 2026-08-13 22:08:47 UTC
Parallelism
80/100
Blocked
87%
Avg conflicts / tx
2.96
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #95,746,413 · 98 txs across 20 waves · depth 20
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
wave w19
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w25w39w310w411w512w613w714w815w916w1024w877w1581w1682w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
24 touches
66 conflicts
0x889d5e90…929a
0x2a68ba…90c5
20 touches
45 conflicts
0x17606ba6…1b6e
0x754704…b603
20 touches
45 conflicts
0xffa7d0a4…b10a
0x40c49f…2af0
16 touches
28 conflicts
0xe75ce681…ba5f
0x188d58…ea8e
14 touches
21 conflicts
0xe75ce681…ba60
0x188d58…ea8e
14 touches
21 conflicts
0x002fed35…79fa
0x2a68ba…90c5
14 touches
21 conflicts
0x66d5e476…8a1f
0x34b655…2a6f
14 touches
21 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
66 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity