pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,868,994
← previous block
next block →
recent activity
Analyzing
Block #94,868,994
16 transactions · 16 stateful · 2026-08-10 20:20:05 UTC
Parallelism
88
/100
Blocked
6
%
Avg conflicts / tx
0.06
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,868,994
· 16 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#3
updatePrices
#4
execFwdPositionOps
#5
execFwdPositionOps
#6
exec
#7
0x6a7a32ed
#8
setData
#9
execOrders
#10
execOrders
#11
execOrders
#12
execOrders
#13
execOrders
#14
execOrders
#15
0x59558d29
#2
execOrders
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
0x30a41252…2f10
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x23153440…0007
0x34b655…2a6f
3 touches
1 conflict
0x4bc1abab…5874
0x34b655…2a6f
3 touches
1 conflict
0x2a1544ad…9f70
0x34b655…2a6f
2 touches
0 conflicts
0x2e153698…5b40
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
0x30a412529c…e32f10
Audit this contract →
← previous block
·
next block →
recent activity