pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,676,240
← previous block
next block →
recent activity
Analyzing
Block #93,676,240
10 transactions · 8 stateful · 2026-08-06 16:03:33 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,676,240
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 1
#3
updatePriceFeedsIfNecessary
#4
0x3f5c179b
#5
execFwdPositionOps
#6
updateDataFeedsValuesPartial
#7
setData
#8
0xd9eae7…136e
#9
execOrders
#2
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x954ff78d…93b4
0x34b655…2a6f
4 touches
1 conflict
0xc6000ba5…8d65
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0dba35c5…5b77
0x34b655…2a6f
2 touches
0 conflicts
0x13c41ef7…325a
0x34b655…2a6f
2 touches
0 conflicts
0x1a4437ae…c776
0x34b655…2a6f
2 touches
0 conflicts
0x1cdfe548…d3aa
0x34b655…2a6f
2 touches
0 conflicts
0x1db9ae71…2888
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
0x954ff78d9d…2593b4
Audit this contract →
← previous block
·
next block →
recent activity