pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,914,915
← previous block
next block →
recent activity
Analyzing
Block #98,914,915
10 transactions · 10 stateful · 2026-08-25 01:38:33 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,914,915
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
setData
#2
0xab083028
#3
execOrders
#4
0x59558d29
#5
execFwdPositionOpsV2
· blocks 1
#6
0x3f5c179b
#8
execFwdPositionOpsV2
#9
execOrders
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0xd6c976a1…1d47
0x34b655…2a6f
4 touches
1 conflict
0xd6c976a1…1d48
0x34b655…2a6f
4 touches
1 conflict
0x10ca7c55…c28d
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x1b19e8c4…13ec
0x34b655…2a6f
3 touches
1 conflict
0xb55a7cbc…68f5
0x2b46c0…1669
2 touches
0 conflicts
0xbbca528a…1b10
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
0x326a02b5c5…5c8dad
Audit this contract →
← previous block
·
next block →
recent activity