pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#81,633,313
← previous block
next block →
recent activity
Analyzing
Block #81,633,313
12 transactions · 10 stateful · 2026-06-16 09:34:24 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#81,633,313
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
approve
· blocks 1
#3
updateDataFeedsValuesPartial
#4
updatePrices
#5
approve
#6
forward
#7
0xe1d28d…bb05
#8
0x657982…7dbc
#9
setData
#10
execOrders
#11
0xc7e3ec2c
#2
deposit
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb182933f…46ed
0x754704…b603
2 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x213a54fa…c85f
0x34b655…2a6f
2 touches
0 conflicts
0x6f58168d…ea24
0x34b655…2a6f
2 touches
0 conflicts
0x74fd0a9b…3aaa
0x34b655…2a6f
2 touches
0 conflicts
0x7506443a…4820
0x34b655…2a6f
2 touches
0 conflicts
0xd98b3c10…67b8
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)
1 conflict on slot
0xb182933f52…6846ed
Audit this contract →
← previous block
·
next block →
recent activity