pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,456,159
← previous block
next block →
recent activity
Analyzing
Block #100,456,159
10 transactions · 10 stateful · 2026-08-30 11:20:05 UTC
Parallelism
50
/100
Blocked
40
%
Avg conflicts / tx
1
Longest chain
5
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,456,159
· 10 txs across 5 waves · depth 5
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
transferWithAuthorization
· blocks 4
#7
setData
#8
execFwdPositionOpsV2
#9
0xed82b078
#3
transferWithAuthorization
· blocks 3
#4
transferWithAuthorization
· blocks 2
#5
transferWithAuthorization
· blocks 1
#6
transferWithAuthorization
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
5
w3
6
w4
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd17580f9…ece1
0x754704…b603
10 touches
10 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x025fef2f…9738
0x34b655…2a6f
2 touches
0 conflicts
0x0eac7709…66c3
0x34b655…2a6f
2 touches
0 conflicts
0x23529e13…6f25
0x34b655…2a6f
2 touches
0 conflicts
0x091bd919…8794
0x754704…b603
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:
USDC (USDC)
10 conflicts on slot
0xd17580f913…78ece1
Audit this contract →
← previous block
·
next block →
recent activity