pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,675,512
← previous block
next block →
recent activity
Analyzing
Block #94,675,512
7 transactions · 4 stateful · 2026-08-10 04:05:21 UTC
Parallelism
71
/100
Blocked
25
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,675,512
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#2
0xeb282f7f
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#6
0x61d59c2d
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2e52e46…0894
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x124776d6…49b4
0x34b655…2a6f
2 touches
0 conflicts
0x2623ecd3…2b14
0x34b655…2a6f
2 touches
0 conflicts
0x2860b9bb…282c
0x34b655…2a6f
2 touches
0 conflicts
0x2d307ea7…8841
0x34b655…2a6f
2 touches
0 conflicts
0x2df168a5…cc6c
0x34b655…2a6f
2 touches
0 conflicts
0x46483cb1…e7ca
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
0xe2e52e4663…6f0894
Audit this contract →
← previous block
·
next block →
recent activity