pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,535,764
← previous block
next block →
recent activity
Analyzing
Block #98,535,764
11 transactions · 11 stateful · 2026-08-23 17:21:42 UTC
Parallelism
82
/100
Blocked
18
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,535,764
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#2
0x59558d29
#3
execPerpOps
· blocks 1
#6
execFwdPositionOpsV2
#7
0x3f5c179b
#8
0xed82b078
#9
0xed82b078
#10
setData
#4
execPerpOps
#5
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w0
4
w1
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6ca15e14…7be8
0x34b655…2a6f
4 touches
1 conflict
0xa02838a3…bc54
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x054b1ea3…f33a
0x34b655…2a6f
2 touches
0 conflicts
0x06c8fd5b…110f
0x34b655…2a6f
2 touches
0 conflicts
0x0b0611f7…e63a
0x34b655…2a6f
2 touches
0 conflicts
0x0eac7709…66c3
0x34b655…2a6f
2 touches
0 conflicts
0x0f15f74f…8d71
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
0x6ca15e14f4…917be8
Audit this contract →
← previous block
·
next block →
recent activity