pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,676,560
← previous block
next block →
recent activity
Analyzing
Block #98,676,560
6 transactions · 6 stateful · 2026-08-24 05:35:24 UTC
Parallelism
67
/100
Blocked
17
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,676,560
· 6 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOpsV2
#2
forward
#3
execFwdPositionOpsV2
· blocks 1
#5
0x6a8bd893
#4
execFwdPositionOpsV2
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
0x7da79812…d73d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x9de538e5…7632
0x34b655…2a6f
4 touches
1 conflict
0x9de538e5…7633
0x34b655…2a6f
4 touches
1 conflict
0x1d9e1b2d…329a
0x34b655…2a6f
4 touches
1 conflict
0x07e3a406…95f6
0x34b655…2a6f
3 touches
1 conflict
0x1d05417b…42e2
0x34b655…2a6f
2 touches
0 conflicts
0x261cbea7…e35d
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
0x7da798129b…c6d73d
Audit this contract →
← previous block
·
next block →
recent activity