pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,477,662
← previous block
next block →
recent activity
Analyzing
Block #94,477,662
10 transactions · 9 stateful · 2026-08-09 11:30:15 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,477,662
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
execOrders
#3
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
#6
batchUpdate
#7
updateDataFeedsValuesPartial
#8
0x6a78653e
#9
setData
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1ffbed17…4f3c
0x34b655…2a6f
4 touches
1 conflict
0xc1f6acda…6abb
0x34b655…2a6f
4 touches
1 conflict
0xc93761d9…cfdf
0x34b655…2a6f
4 touches
1 conflict
0x16e09de0…4efe
0x34b655…2a6f
2 touches
0 conflicts
0x24b6091e…d294
0x34b655…2a6f
2 touches
0 conflicts
0x28129e3f…47a9
0x34b655…2a6f
2 touches
0 conflicts
0x3377da70…01e5
0x34b655…2a6f
2 touches
0 conflicts
0x4f1ad4b4…e00a
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
0x1ffbed17be…0a4f3c
Audit this contract →
← previous block
·
next block →
recent activity