pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,038,358
← previous block
next block →
recent activity
Analyzing
Block #99,038,358
10 transactions · 10 stateful · 2026-08-25 12:02:42 UTC
Parallelism
80
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,038,358
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
delegate
#2
0x59558d29
#3
execFwdPositionOpsV2
· blocks 1
#5
execFwdPositionOpsV2
#6
0xed82b078
#7
0xed82b078
#8
execOrders
· blocks 1
#4
execFwdPositionOpsV2
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x81e1b637…2b3b
0x34b655…2a6f
4 touches
1 conflict
0x81e1b637…2b3c
0x34b655…2a6f
4 touches
1 conflict
0xc967eefd…fe29
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc3baa205…f26e
0x34b655…2a6f
4 touches
1 conflict
0xaca60768…7272
0x34b655…2a6f
4 touches
1 conflict
0x295780b7…d2d1
0x34b655…2a6f
4 touches
1 conflict
0x3234b328…684a
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
1 conflict on slot
0x81e1b63766…662b3b
Audit this contract →
← previous block
·
next block →
recent activity