pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,127,439
← previous block
next block →
recent activity
Analyzing
Block #100,127,439
11 transactions · 10 stateful · 2026-08-29 07:41:57 UTC
Parallelism
73
/100
Blocked
20
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,127,439
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5acec890
#2
setData
#3
0x3f5c179b
#4
0x3f5c179b
#5
execFwdPositionOpsV2
#6
0x94defb17
· blocks 2
#9
0x6a928dbd
#10
execOrders
#7
0x94defb17
· blocks 1
#8
bet
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
0x2a07e64e…fe77
0x754704…b603
6 touches
3 conflicts
0x00000000…0008
0x8964d7…10f8
6 touches
3 conflicts
0x9d6c2e85…664c
0x8964d7…10f8
4 touches
1 conflict
0x9d6c2e85…664d
0x8964d7…10f8
4 touches
1 conflict
0x9d6c2e85…6650
0x8964d7…10f8
4 touches
1 conflict
0x9d6c2e85…6651
0x8964d7…10f8
4 touches
1 conflict
0x177211e2…1c2d
0x754704…b603
4 touches
1 conflict
0x00000000…003d
0x447d2e…e9f5
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
0x2a07e64ef2…a8fe77
Audit this contract →
← previous block
·
next block →
recent activity