pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,999,010
← previous block
next block →
recent activity
Analyzing
Block #98,999,010
13 transactions · 10 stateful · 2026-08-25 08:41:55 UTC
Parallelism
85
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,999,010
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updatePrices
#3
updatePrices
#4
updatePrices
#5
0x6a8d55cb
· blocks 1
#6
0x6ad2e98b
#8
0x59558d29
#9
batchUpdate
#10
execFwdPositionOpsV2
#11
setData
#12
execOrders
#7
0x6a8d55cb
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x002fed35…79fa
0x2a68ba…90c5
2 touches
0 conflicts
0x6518075e…2b17
0x2a68ba…90c5
2 touches
0 conflicts
0x359866c7…de7b
0x34b655…2a6f
2 touches
0 conflicts
0x845ec8b0…c1af
0x34b655…2a6f
2 touches
0 conflicts
0xb0149c7a…22cb
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:
0x681e908b…e1ae09
1 conflict on slot
0x0d622e34f9…000000
Audit this contract →
← previous block
·
next block →
recent activity