← previous blocknext block →recent activity
Analyzing
Block #95,527,748
14 transactions · 13 stateful · 2026-08-13 03:47:54 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,527,748 · 14 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
1w02w13w24w36w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xbde524f4…43bf
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x5b763734…68e3
0x34b655…2a6f
5 touches
3 conflicts
0x705ab4ae…0162
0x34b655…2a6f
5 touches
3 conflicts
0xb371802a…310c
0x34b655…2a6f
4 touches
1 conflict
0x2c7064fa…682d
0x34b655…2a6f
2 touches
0 conflicts
0x356b3121…cf1c
0x34b655…2a6f
2 touches
0 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
6 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity