pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,674,001
← previous block
next block →
recent activity
Analyzing
Block #94,674,001
9 transactions · 8 stateful · 2026-08-10 03:57:45 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,674,001
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 1
#2
updateDataFeedsValuesPartial
#4
execFwdPositionOps
#5
execFwdPositionOps
#6
forward
#7
setData
#8
0x6a794cb1
#3
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd064a456…b881
0x34b655…2a6f
4 touches
1 conflict
0x0d9bb98e…c3b9
0x34b655…2a6f
4 touches
1 conflict
0x8a72da7b…5b2a
0x34b655…2a6f
4 touches
1 conflict
0x539ac47f…eb6f
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x344bc09a…942f
0x34b655…2a6f
2 touches
0 conflicts
0x4327afd2…1b3a
0x34b655…2a6f
2 touches
0 conflicts
0x557ac419…8fc4
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
0xd064a456fe…30b881
Audit this contract →
← previous block
·
next block →
recent activity