pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,739,297
← previous block
next block →
recent activity
Analyzing
Block #94,739,297
11 transactions · 10 stateful · 2026-08-10 09:26:36 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,739,297
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
multicall
#3
execOrder
· blocks 2
#6
updateDataFeedsValuesPartial
#7
execFwdPositionOps
#8
execFwdPositionOps
#9
setData
#10
0xc7e3ec2c
#4
execOrder
#5
execOrder
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4f1ad4b4…e00a
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x128bb45b…7cb1
0x065c9d…c394
2 touches
0 conflicts
0x153148c9…04ca
0x065c9d…c394
2 touches
0 conflicts
0x71392f15…148d
0x065c9d…c394
2 touches
0 conflicts
0xb33ff823…1188
0x065c9d…c394
2 touches
0 conflicts
0xdc0004e5…61ed
0x065c9d…c394
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
0x4f1ad4b4ec…b9e00a
Audit this contract →
← previous block
·
next block →
recent activity