pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,858,020
← previous block
next block →
recent activity
Analyzing
Block #94,858,020
11 transactions · 9 stateful · 2026-08-10 19:24:53 UTC
Parallelism
73
/100
Blocked
22
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,858,020
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5acec890
· blocks 2
#2
0x5acec890
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
setData
#7
execFwdPositionOps
#8
execFwdPositionOps
#9
0x6a7a25fd
#3
execOrders
· blocks 1
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
10
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x72ed31c7…de4d
0x34b655…2a6f
6 touches
3 conflicts
0x65f90aa4…c97f
0x34b655…2a6f
4 touches
1 conflict
0x0f2d78b1…7363
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xae28870c…072f
0x34b655…2a6f
4 touches
1 conflict
0x3e4af36e…07ae
0x34b655…2a6f
3 touches
1 conflict
0x31efecb1…b00e
0x34b655…2a6f
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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
3 conflicts on slot
0x72ed31c78b…48de4d
Audit this contract →
← previous block
·
next block →
recent activity