pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,353,581
← previous block
next block →
recent activity
Analyzing
Block #98,353,581
13 transactions · 13 stateful · 2026-08-23 01:57:54 UTC
Parallelism
77
/100
Blocked
15
%
Avg conflicts / tx
0.15
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,353,581
· 13 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x6a8a541a
#2
updatePrices
#3
0xab083028
#4
execOrders
#5
0x59558d29
#6
0x5acec890
· blocks 1
#8
execFwdPositionOpsV2
#9
forward
#10
forward
#11
setData
#7
0x5acec890
· blocks 1
#12
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
12
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x3e49348b…9445
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x1408e7c7…f324
0x34b655…2a6f
2 touches
0 conflicts
0x88639b0c…45b2
0x34b655…2a6f
2 touches
0 conflicts
0x9210e826…1414
0x34b655…2a6f
2 touches
0 conflicts
0xadb553c0…430a
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
0xca841faae5…71486a
Audit this contract →
← previous block
·
next block →
recent activity