pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,797,790
← previous block
next block →
recent activity
Analyzing
Block #94,797,790
11 transactions · 9 stateful · 2026-08-10 14:21:52 UTC
Parallelism
82
/100
Blocked
22
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,797,790
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#3
0x5acec890
#4
execFwdPositionOps
· blocks 1
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
setData
#10
0xc7e3ec2c
#2
0x6ad2e98b
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x320fe488…568e
0x34b655…2a6f
4 touches
1 conflict
0x74e46435…fdcd
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xb2560305…f27d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xccebf5c5…8758
0x34b655…2a6f
4 touches
1 conflict
0xe4af4c87…9964
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
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
0x320fe488ec…53568e
Audit this contract →
← previous block
·
next block →
recent activity