pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,316,576
← previous block
next block →
recent activity
Analyzing
Block #99,316,576
8 transactions · 8 stateful · 2026-08-26 11:26:07 UTC
Parallelism
75
/100
Blocked
38
%
Avg conflicts / tx
0.38
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,316,576
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
0x5acec890
· blocks 1
#4
execFwdPositionOpsV2
· blocks 2
#7
setData
#3
0x5acec890
#5
execFwdPositionOpsV2
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w0
5
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5164ab0e…01e1
0xc8689a…ee79
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x76622fb2…4f08
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xea57afd0…4232
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x43b34fb2…7b88
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: Settlement / Helper
1 conflict on slot
0x5164ab0e04…c201e1
Audit this contract →
← previous block
·
next block →
recent activity