pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,815,657
← previous block
next block →
recent activity
Analyzing
Block #94,815,657
12 transactions · 12 stateful · 2026-08-10 15:51:46 UTC
Parallelism
83
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,815,657
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrder
· blocks 1
#2
0x5acec890
#3
execFwdPositionOps
#4
0x3f5c179b
#5
batchUpdate
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
0x6a79f409
#10
setData
#11
execOrders
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x15c22181…1354
0x34b655…2a6f
2 touches
0 conflicts
0x1c92402e…37cf
0x34b655…2a6f
2 touches
0 conflicts
0x30932529…5ab2
0x34b655…2a6f
2 touches
0 conflicts
0x4102cb2a…3b17
0x34b655…2a6f
2 touches
0 conflicts
0x4327afd2…1b3a
0x34b655…2a6f
2 touches
0 conflicts
0x50afedcd…91cc
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
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity