pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,276,559
← previous block
next block →
recent activity
Analyzing
Block #98,276,559
10 transactions · 10 stateful · 2026-08-22 19:30:23 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,276,559
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x59558d29
#3
0x928e4afa
· blocks 1
#5
swap
#6
execFwdPositionOpsV2
#7
0xed82b078
#8
0xed82b078
#9
setData
#4
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xad3e66be…dccc
0xc8689a…ee79
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xe98c5817…9f9f
0x34b655…2a6f
4 touches
1 conflict
0xfaefdbf4…bf65
0x34b655…2a6f
4 touches
1 conflict
0x00f19757…9252
0x34b655…2a6f
4 touches
1 conflict
0x2ad40921…083a
0x34b655…2a6f
4 touches
1 conflict
0x2d94ecd9…43db
0x34b655…2a6f
4 touches
1 conflict
0x34d95d94…3a16
0x34b655…2a6f
4 touches
1 conflict
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: Settlement / Helper
1 conflict on slot
0xad3e66bedd…10dccc
Audit this contract →
← previous block
·
next block →
recent activity