pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,826,474
← previous block
next block →
recent activity
Analyzing
Block #97,826,474
14 transactions · 14 stateful · 2026-08-21 05:31:59 UTC
Parallelism
86
/100
Blocked
7
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,826,474
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
#2
0xab083028
#3
execOrders
· blocks 1
#5
executeBatch
#6
execFwdPositionOpsV2
#7
0x3f5c179b
#8
execFwdPositionOpsV2
#9
forward
#10
execFwdPositionOpsV2
#11
setData
#12
0x61d59c2d
#13
execOrders
#4
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0xe09e365c…b22d
0x34b655…2a6f
4 touches
1 conflict
0xe188ad90…d23f
0x34b655…2a6f
4 touches
1 conflict
0xe2341c33…934c
0x34b655…2a6f
4 touches
1 conflict
0x2407edc1…f2c8
0x34b655…2a6f
4 touches
1 conflict
0xbb97db90…4c93
0xc8689a…ee79
2 touches
0 conflicts
0x04c8137b…e776
0xe52b14…7230
2 touches
0 conflicts
0x04c8137b…e778
0xe52b14…7230
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
0x8bf661cb38…d4bcd2
Audit this contract →
← previous block
·
next block →
recent activity