pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,719,490
← previous block
next block →
recent activity
Analyzing
Block #94,719,490
10 transactions · 9 stateful · 2026-08-10 07:46:33 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,719,490
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0x3f5c179b
#5
executeBatch
#6
0xd62522e3
#7
execFwdPositionOps
· blocks 1
#9
0x40f790…07ba
#8
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6176fff…d2c5
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xbde1af1b…9adf
0x34b655…2a6f
4 touches
1 conflict
0x0e37797c…d724
0x34b655…2a6f
2 touches
0 conflicts
0x3a15f0fa…d60a
0x34b655…2a6f
2 touches
0 conflicts
0x41377979…0a18
0x34b655…2a6f
2 touches
0 conflicts
0x81561f70…fefd
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
0xa6176fffd8…fcd2c5
Audit this contract →
← previous block
·
next block →
recent activity