← previous blocknext block →recent activity
Analyzing
Block #95,902,811
14 transactions · 13 stateful · 2026-08-14 11:15:35 UTC
Parallelism
50/100
Blocked
54%
Avg conflicts / tx
1.57
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #95,902,811 · 14 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w36w47w08w510w611w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x8a5ced1c…3b29
0x34b655…2a6f
10 touches
10 conflicts
0x97862f28…4ede
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xadc05b3e…378d
0x34b655…2a6f
8 touches
6 conflicts
0x4188cc5f…2d2e
0x34b655…2a6f
6 touches
3 conflicts
0x66473027…6780
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity