pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,365,431
← previous block
next block →
recent activity
Analyzing
Block #98,365,431
12 transactions · 11 stateful · 2026-08-23 02:57:31 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,365,431
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
approve
· blocks 1
#3
0xa96df62f
#4
0xab083028
#5
0x59558d29
#6
0x0c7abd22
#7
0x5acec890
#8
execFwdPositionOpsV2
#9
execFwdPositionOpsV2
#10
execFwdPositionOpsV2
#11
setData
#2
swap
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x12f908ed…6c6e
0x0158ab…1a70
2 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x20b50479…b75c
0x0158ab…1a70
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0000
0x0c428e…07a4
2 touches
0 conflicts
0x00000000…0001
0x0c428e…07a4
2 touches
0 conflicts
0x00000000…0003
0x0c428e…07a4
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:
0x0158abff…731a70
1 conflict on slot
0x12f908ed33…e56c6e
Audit this contract →
← previous block
·
next block →
recent activity