pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,472,433
← previous block
next block →
recent activity
Analyzing
Block #93,472,433
13 transactions · 12 stateful · 2026-08-05 22:59:00 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,472,433
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
updateDataFeedsValuesPartial
#3
aggregate3
#4
execFwdPositionOps
#5
placeAndExecuteMarketBuy
#6
0x94defb17
#7
execOrders
#8
execFwdPositionOps
#9
setData
· blocks 1
#11
0x59558d29
#12
0xc7e3ec2c
#10
setData
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…0004
0x026864…26e6
2 touches
0 conflicts
0x00f245ce…1e10
0x34b655…2a6f
2 touches
0 conflicts
0x075dcfb7…1c3b
0x34b655…2a6f
2 touches
0 conflicts
0x0960ac51…5440
0x34b655…2a6f
2 touches
0 conflicts
0x1507536e…933f
0x34b655…2a6f
2 touches
0 conflicts
0x154ced50…37b1
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:
0x33176be2…ede078
1 conflict on slot
0x09106a952c…111467
Audit this contract →
← previous block
·
next block →
recent activity