pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,266,417
← previous block
next block →
recent activity
Analyzing
Block #93,266,417
12 transactions · 11 stateful · 2026-08-05 05:43:12 UTC
Parallelism
83
/100
Blocked
18
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,266,417
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a72cde8
#2
updatePrices
· blocks 1
#4
0x5acec890
#5
updateDataFeedsValuesPartial
#6
execFwdPositionOps
· blocks 1
#8
execFwdPositionOps
#9
transfer
#10
setData
#11
0xc7e3ec2c
#3
updatePrices
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x793aa64d…b09c
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09d
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x91855e…ac7e
4 touches
1 conflict
0xc1da8f73…484c
0x34b655…2a6f
4 touches
1 conflict
0x1719c655…6592
0x34b655…2a6f
2 touches
0 conflicts
0x8765edd1…a7d5
0x34b655…2a6f
2 touches
0 conflicts
0xe8377f79…5f5e
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
0x793aa64d0d…fdb09c
Audit this contract →
← previous block
·
next block →
recent activity