pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,207,293
← previous block
next block →
recent activity
Analyzing
Block #98,207,293
13 transactions · 8 stateful · 2026-08-22 13:41:55 UTC
Parallelism
85
/100
Blocked
13
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,207,293
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x0c7abd22
#3
0x7b84f330
#4
execOrders
#5
updatePrices
#6
execOrder
#7
0x59558d29
#8
forward
#9
execFwdPositionOpsV2
#10
setData
· blocks 1
#12
0x7b84f330
#11
setData
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b621a7d…2611
0x34b655…2a6f
2 touches
0 conflicts
0x14cc77c7…69c4
0x34b655…2a6f
2 touches
0 conflicts
0x14ee2daf…a775
0x34b655…2a6f
2 touches
0 conflicts
0x18b65823…058d
0x34b655…2a6f
2 touches
0 conflicts
0x2860b9bb…282c
0x34b655…2a6f
2 touches
0 conflicts
0x391d75c5…b826
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:
0x33176be2…ede078
1 conflict on slot
0x09106a952c…111467
Audit this contract →
← previous block
·
next block →
recent activity