pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,701,956
← previous block
next block →
recent activity
Analyzing
Block #100,701,956
11 transactions · 8 stateful · 2026-08-31 07:56:33 UTC
Parallelism
73
/100
Blocked
25
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,701,956
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5acec890
#2
0x59558d29
#3
0x59558d29
#4
execOrders
#5
execFwdPositionOpsV2
#6
transferWithAuthorization
· blocks 2
#9
setData
#10
execOrders
#7
transferWithAuthorization
· blocks 1
#8
transferWithAuthorization
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0ed7cc0b…ee52
0x34b655…2a6f
2 touches
0 conflicts
0x23529e13…6f25
0x34b655…2a6f
2 touches
0 conflicts
0x24124b5e…9891
0x34b655…2a6f
2 touches
0 conflicts
0x5e4ed8fb…2d93
0x34b655…2a6f
2 touches
0 conflicts
0x64a785e4…0110
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:
USDC (USDC)
3 conflicts on slot
0xd17580f913…78ece1
Audit this contract →
← previous block
·
next block →
recent activity