pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,086,738
← previous block
next block →
recent activity
Analyzing
Block #96,086,738
7 transactions · 7 stateful · 2026-08-15 02:41:02 UTC
Parallelism
57
/100
Blocked
29
%
Avg conflicts / tx
0.43
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,086,738
· 7 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrders
#2
0x94defb17
· blocks 2
#5
setData
#6
execOrders
#3
0x94defb17
· blocks 1
#4
0x8b80a919
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x177211e2…1c2d
0x754704…b603
6 touches
3 conflicts
0xe6b9f9a4…adbf
0x968279…9342
4 touches
1 conflict
0x521a5982…a82a
0x754704…b603
4 touches
1 conflict
0x00000000…0006
0x968279…9342
4 touches
1 conflict
0xabbdcd04…dd9d
0x968279…9342
4 touches
1 conflict
0xabbdcd04…dd9e
0x968279…9342
4 touches
1 conflict
0xabbdcd04…dda1
0x968279…9342
4 touches
1 conflict
0xabbdcd04…dda2
0x968279…9342
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:
USDC (USDC)
3 conflicts on slot
0x177211e248…161c2d
Audit this contract →
← previous block
·
next block →
recent activity