pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,501,448
← previous block
next block →
recent activity
Analyzing
Block #93,501,448
13 transactions · 12 stateful · 2026-08-06 01:24:52 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,501,448
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#2
updatePrices
#3
0xeb282f7f
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
0xb2d4797b
#7
placeAndExecuteMarketBuy
#8
0x94defb17
#10
0x6a73e2dc
#11
setData
#12
0xc7e3ec2c
#9
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x52b477bc…7ccf
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xa67b76d8…97ff
0x1efe02…37d6
2 touches
0 conflicts
0x2c0fe9aa…dad9
0x34b655…2a6f
2 touches
0 conflicts
0xbde524f4…43bf
0x34b655…2a6f
2 touches
0 conflicts
0xc962f660…56c0
0x34b655…2a6f
2 touches
0 conflicts
0xdbb9cf89…166c
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:
Perpl
1 conflict on slot
0x52b477bcb8…5d7ccf
Audit this contract →
← previous block
·
next block →
recent activity