pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,175,720
← previous block
next block →
recent activity
Analyzing
Block #84,175,720
10 transactions · 9 stateful · 2026-06-28 04:24:21 UTC
Parallelism
60
/100
Blocked
33
%
Avg conflicts / tx
0.6
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,175,720
· 10 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
updatePrices
#2
execFwdPositionOps
#3
updateDataFeedsValuesPartial
#4
transferWithAuthorization
· blocks 3
#8
0x6a40a26d
#9
setData
#5
transferWithAuthorization
· blocks 2
#6
transferWithAuthorization
· blocks 1
#7
transferWithAuthorization
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w2
7
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd0031975…cbe2
0x754704…b603
8 touches
6 conflicts
0xb9593682…3806
0x754704…b603
8 touches
6 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x09500602…94e9
0x34b655…2a6f
2 touches
0 conflicts
0x09500602…94ea
0x34b655…2a6f
2 touches
0 conflicts
0x0f53de2c…9c58
0x34b655…2a6f
2 touches
0 conflicts
0x17ad8913…0339
0x34b655…2a6f
2 touches
0 conflicts
0x18c25abf…8bef
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)
6 conflicts on slot
0xd003197509…3acbe2
Audit this contract →
← previous block
·
next block →
recent activity