pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,414,764
← previous block
next block →
recent activity
Analyzing
Block #95,414,764
14 transactions · 13 stateful · 2026-08-12 18:19:24 UTC
Parallelism
86
/100
Blocked
15
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,414,764
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
matchOrders
· blocks 1
#5
0xa96df62f
#6
0x5acec890
#7
execOrders
#8
0x3f5c179b
#9
updateDataFeedsValuesPartial
#10
updateDataFeedsValuesPartial
#11
transfer
#12
setData
#13
0x59558d29
#2
0x0c7abd22
#4
matchOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa949d556…184c
0x754704…b603
4 touches
1 conflict
0xef712f4a…0853
0x99c7a7…8bf0
4 touches
1 conflict
0x4dbb0f3e…2028
0x99c7a7…8bf0
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
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)
1 conflict on slot
0xa949d556b1…83184c
Audit this contract →
← previous block
·
next block →
recent activity