← previous blocknext block →recent activity
Analyzing
Block #95,710,929
15 transactions · 14 stateful · 2026-08-13 19:10:09 UTC
Parallelism
73/100
Blocked
43%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,710,929 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w18w29w110w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbb320b04…15b1
0x34b655…2a6f
8 touches
6 conflicts
0x442e26a3…e968
0x34b655…2a6f
6 touches
3 conflicts
0xab29fc62…9506
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x24b08f9c…e594
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x4c619b7d…f4fa
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
6 conflicts on slot 0xbb320b04a6…0a15b1
Audit this contract →
← previous block·next block →recent activity