← previous blocknext block →recent activity
Analyzing
Block #95,648,098
51 transactions · 47 stateful · 2026-08-13 13:53:15 UTC
Parallelism
71/100
Blocked
77%
Avg conflicts / tx
2.45
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #95,648,098 · 51 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w07w18w218w320w721w122w123w225w326w427w528w629w830w939w241w342w1045w346w1147w1248w1349w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xeae24c…0be0
14 touches
21 conflicts
0x0a57a2b8…3cdd
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xa779293b…5e59
0x34b655…2a6f
12 touches
15 conflicts
0xec7d120d…7084
0x34b655…2a6f
10 touches
10 conflicts
0x987f3723…1bff
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x66d5e476…8a1f
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: 0xeae24c72…e30be0
21 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity