pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,466,247
← previous block
next block →
recent activity
Analyzing
Block #94,466,247
14 transactions · 13 stateful · 2026-08-09 10:32:47 UTC
Parallelism
86
/100
Blocked
8
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,466,247
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xb97bc0…e828
#2
execFwdPositionOps
· blocks 1
#3
0x765aeb4f
#5
batchUpdate
#6
transfer
#7
setData
#8
execOrders
#9
execOrders
#10
execOrders
#11
execOrders
#12
execOrders
#13
0xc7e3ec2c
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0e22f39d…b92b
0x34b655…2a6f
4 touches
1 conflict
0x22866298…d604
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc4ac7154…0aeb
0x34b655…2a6f
4 touches
1 conflict
0x0f06b859…7a89
0x34b655…2a6f
3 touches
1 conflict
0x16838830…6ab2
0x34b655…2a6f
2 touches
0 conflicts
0x2b75d304…d186
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
1 conflict on slot
0x0e22f39dda…aab92b
Audit this contract →
← previous block
·
next block →
recent activity