pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,099,639
← previous block
next block →
recent activity
Analyzing
Block #99,099,639
13 transactions · 13 stateful · 2026-08-25 17:14:34 UTC
Parallelism
85
/100
Blocked
15
%
Avg conflicts / tx
0.23
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,099,639
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
0x59558d29
#3
execFwdPositionOpsV2
· blocks 1
#4
execFwdPositionOpsV2
· blocks 1
#5
0x3f5c179b
#6
0x94defb17
· blocks 1
#7
0xed82b078
#10
transfer
#11
setData
#12
execOrders
#8
execFwdPositionOpsV2
#9
bet
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w0
6
w0
8
w1
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x2a07e64e…fe77
0x754704…b603
4 touches
1 conflict
0x00000000…0008
0x8964d7…10f8
4 touches
1 conflict
0x3af99706…db23
0x8964d7…10f8
4 touches
1 conflict
0x3af99706…db24
0x8964d7…10f8
4 touches
1 conflict
0x3af99706…db27
0x8964d7…10f8
4 touches
1 conflict
0x3af99706…db28
0x8964d7…10f8
4 touches
1 conflict
0x5c455afd…ce06
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
0x482471adbb…39122f
Audit this contract →
← previous block
·
next block →
recent activity