pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,684,426
← previous block
next block →
recent activity
Analyzing
Block #94,684,426
11 transactions · 10 stateful · 2026-08-10 04:50:11 UTC
Parallelism
73
/100
Blocked
30
%
Avg conflicts / tx
0.36
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,684,426
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
execOrders
· blocks 2
#3
updatePrices
#7
updateDataFeedsValuesPartial
#8
updatePosition
#9
0x6a7958fb
#10
setData
#4
0x5acec890
· blocks 2
#5
0x5acec890
#6
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
5
w2
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2e52e46…0894
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xf18575c0…880c
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x18978822…2623
0x34b655…2a6f
2 touches
0 conflicts
0x333300cc…04fe
0x34b655…2a6f
2 touches
0 conflicts
0x38c6ff01…689f
0x34b655…2a6f
2 touches
0 conflicts
0x4069c511…21c8
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
3 conflicts on slot
0xe2e52e4663…6f0894
Audit this contract →
← previous block
·
next block →
recent activity