pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,725,838
← previous block
next block →
recent activity
Analyzing
Block #97,725,838
11 transactions · 11 stateful · 2026-08-20 21:04:06 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
#97,725,838
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x7b84f330
· blocks 1
#2
0x9cf9a051
#3
execOrders
#4
0xab083028
#5
0x45b7e41f
#6
execFwdPositionOpsV2
· blocks 1
#7
setData
#8
0x59558d29
#9
execOrders
#10
0x7b84f330
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w0
9
w1
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x00000000…0002
0x08dd3d…a583
2 touches
0 conflicts
0xff9eec93…1598
0x08dd3d…a583
2 touches
0 conflicts
0x00000000…0003
0x0a4fcb…a602
2 touches
0 conflicts
0x9c53d1d8…4203
0x0a4fcb…a602
2 touches
0 conflicts
0xc2575a0e…f887
0x0a4fcb…a602
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
0x7aad02c682…feb979
Audit this contract →
← previous block
·
next block →
recent activity