pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,940,405
← previous block
next block →
recent activity
Analyzing
Block #98,940,405
10 transactions · 10 stateful · 2026-08-25 03:46:47 UTC
Parallelism
70
/100
Blocked
20
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,940,405
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
execOrders
· blocks 2
#6
0x59558d29
#7
0x3f5c179b
#8
0x6a8d109f
#9
setData
#4
execOrders
· blocks 1
#5
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00390fe5…431c
0x34b655…2a6f
2 touches
0 conflicts
0x12c0be0d…0064
0x34b655…2a6f
2 touches
0 conflicts
0x3a7fb5b5…f0e5
0x34b655…2a6f
2 touches
0 conflicts
0x407ddb5c…958f
0x34b655…2a6f
2 touches
0 conflicts
0x711ed6c5…cebb
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
0xbde524f475…b143bf
Audit this contract →
← previous block
·
next block →
recent activity