← previous blocknext block →recent activity
Analyzing
Block #95,716,995
21 transactions · 20 stateful · 2026-08-13 19:40:49 UTC
Parallelism
71/100
Blocked
45%
Avg conflicts / tx
1.24
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,716,995 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w16w37w111w012w215w419w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08636046…e60f
0x34b655…2a6f
10 touches
10 conflicts
0x734ee320…caae
0x34b655…2a6f
10 touches
10 conflicts
0xafb8e71e…9285
0x34b655…2a6f
8 touches
6 conflicts
0x4deeee1b…8c0c
0x34b655…2a6f
6 touches
3 conflicts
0xd6313d73…483f
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x2c429f11…0652
0x34b655…2a6f
4 touches
1 conflict
0x3cf099ce…2802
0x34b655…2a6f
4 touches
1 conflict
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
10 conflicts on slot 0x08636046fc…69e60f
Audit this contract →
← previous block·next block →recent activity