pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,197,408
← previous block
next block →
recent activity
Analyzing
Block #94,197,408
9 transactions · 9 stateful · 2026-08-08 11:47:58 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,197,408
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
updateDataFeedsValuesPartial
#3
placeAndExecuteMarketBuy
· blocks 1
#5
execFwdPositionOps
#6
execFwdPositionOps
#7
transfer
#8
setData
#4
placeAndExecuteMarketBuy
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xa989d746…7675
0x065c9d…c394
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0x05527801…9c11
0x34b655…2a6f
2 touches
0 conflicts
0x1445ffc7…e961
0x34b655…2a6f
2 touches
0 conflicts
0x28e5dbea…2f7f
0x34b655…2a6f
2 touches
0 conflicts
0x2b856d86…7988
0x34b655…2a6f
2 touches
0 conflicts
0xc2b0a267…8844
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
0xa1087a5ca6…0a66c4
Audit this contract →
← previous block
·
next block →
recent activity