pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,806,638
← previous block
next block →
recent activity
Analyzing
Block #94,806,638
12 transactions · 11 stateful · 2026-08-10 15:06:23 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,806,638
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
0xab083028
#3
0xab083028
#4
execOrder
· blocks 1
#5
0xeb282f7f
#6
execFwdPositionOps
· blocks 1
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#10
forward
#11
setData
#9
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x428b6e5b…8909
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe75ce681…ba60
0x188d58…ea8e
2 touches
0 conflicts
0x3a921be0…779c
0x2a68ba…90c5
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x06ce5d4b…c122
0x2b46c0…1669
2 touches
0 conflicts
0x213ee207…a151
0x2b46c0…1669
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
0x428b6e5b99…c18909
Audit this contract →
← previous block
·
next block →
recent activity