pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,796,661
← previous block
next block →
recent activity
Analyzing
Block #94,796,661
12 transactions · 11 stateful · 2026-08-10 14:16:12 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,796,661
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xaf5e395a
#2
0x5acec890
#3
execFwdPositionOps
· blocks 1
#4
execFwdPositionOps
#6
batchUpdate
#7
forward
#8
updateDataFeedsValuesPartial
#9
0x6a79dda4
#10
setData
#11
execOrders
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4ec9ff52…e6f7
0x34b655…2a6f
4 touches
1 conflict
0xa60eabc0…9f8c
0x34b655…2a6f
4 touches
1 conflict
0xabffe139…e172
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x0a6f5e37…6c3c
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x51ca3051…0972
0x3bd359…433a
2 touches
0 conflicts
0xe65de972…a3c9
0x40c49f…2af0
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
0x4ec9ff52ce…67e6f7
Audit this contract →
← previous block
·
next block →
recent activity