pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,442,871
← previous block
next block →
recent activity
Analyzing
Block #98,442,871
11 transactions · 11 stateful · 2026-08-23 09:27:07 UTC
Parallelism
82
/100
Blocked
27
%
Avg conflicts / tx
0.27
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,442,871
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#2
0x59558d29
#3
execPerpOps
· blocks 1
#5
0x5acec890
· blocks 1
#7
setData
#8
execFwdPositionOpsV2
#9
0x57368ddf
#4
execPerpOps
#6
0x5acec890
#10
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w0
4
w1
5
w0
6
w1
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…1266
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x2acab664…3881
0x065c9d…c394
4 touches
1 conflict
0x5164ab0e…01e1
0xc8689a…ee79
4 touches
1 conflict
0xf3d7a307…4d63
0x065c9d…c394
4 touches
1 conflict
0x45f562b2…9294
0x2b46c0…1669
2 touches
0 conflicts
0x8488f10f…9353
0x2b46c0…1669
2 touches
0 conflicts
0x8488f10f…9354
0x2b46c0…1669
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
0x51fc8795c8…571266
Audit this contract →
← previous block
·
next block →
recent activity