pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,429,811
← previous block
next block →
recent activity
Analyzing
Block #97,429,811
11 transactions · 10 stateful · 2026-08-19 20:01:28 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,429,811
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#2
0x32d01e04
#3
execOrders
#4
execFwdPositionOpsV2
· blocks 1
#6
setData
#7
execFwdPositionOpsV2
#8
0xed82b078
#10
execOrders
#5
execFwdPositionOpsV2
#9
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w0
5
w1
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9413bce8…7963
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x06661beb…fb9b
0x34b655…2a6f
2 touches
0 conflicts
0x128a9311…3dc4
0x34b655…2a6f
2 touches
0 conflicts
0x35ea602c…019a
0x34b655…2a6f
2 touches
0 conflicts
0x3de6ff92…01d7
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
0x9413bce867…817963
Audit this contract →
← previous block
·
next block →
recent activity