pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,501,439
← previous block
next block →
recent activity
Analyzing
Block #93,501,439
11 transactions · 10 stateful · 2026-08-06 01:24:49 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,501,439
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 1
#2
placeAndExecuteMarketSell
#3
0x3f5c179b
#5
0x94defb17
#6
execFwdPositionOps
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
setData
#10
0xc7e3ec2c
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3da3a82e…8a6a
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x6518075e…2b17
0x2a68ba…90c5
2 touches
0 conflicts
0x044844a0…7418
0x34b655…2a6f
2 touches
0 conflicts
0x147b4c97…d770
0x34b655…2a6f
2 touches
0 conflicts
0x1e10796e…6213
0x34b655…2a6f
2 touches
0 conflicts
0x1e10796e…6214
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
0x3da3a82eec…5d8a6a
Audit this contract →
← previous block
·
next block →
recent activity