pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,595,338
← previous block
next block →
recent activity
Analyzing
Block #93,595,338
8 transactions · 7 stateful · 2026-08-06 09:16:50 UTC
Parallelism
75
/100
Blocked
29
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,595,338
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
placeAndExecuteMarketBuy
· blocks 1
#4
verifyOracleProofV2
#5
execFwdPositionOps
· blocks 1
#7
setData
#3
batchUpdate
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4bfdcd51…9b58
0x34b655…2a6f
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0x2b5ab9a3…58c5
0x34b655…2a6f
4 touches
1 conflict
0x5d3f699a…05e4
0x851145…3f07
3 touches
1 conflict
0xf13704e6…258a
0x01bff4…1071
2 touches
0 conflicts
0x00000000…009a
0x16f70c…c3dd
2 touches
0 conflicts
0x72a152dd…9e26
0x16f70c…c3dd
2 touches
0 conflicts
0x07b86c51…cdae
0x2a68ba…90c5
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:
Perpl
1 conflict on slot
0x4bfdcd5135…769b58
Audit this contract →
← previous block
·
next block →
recent activity