pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,674,210
← previous block
next block →
recent activity
Analyzing
Block #94,674,210
10 transactions · 8 stateful · 2026-08-10 03:58:48 UTC
Parallelism
80
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,674,210
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 2
#3
updateDataFeedsValuesPartial
#4
0x3f5c179b
#5
execFwdPositionOps
#6
0x6a794cf0
#7
setData
#9
0xc7e3ec2c
#2
execFwdPositionOps
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf094e5be…d695
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x93b6fab0…09d6
0x34b655…2a6f
4 touches
1 conflict
0x95c47f03…f1bb
0x34b655…2a6f
4 touches
1 conflict
0x36890fff…f3d1
0x34b655…2a6f
2 touches
0 conflicts
0x420429ba…2582
0x34b655…2a6f
2 touches
0 conflicts
0x7ae94b74…7aef
0x34b655…2a6f
2 touches
0 conflicts
0xd75cc64b…2223
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
0xf094e5be0e…6ad695
Audit this contract →
← previous block
·
next block →
recent activity