pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,146,799
← previous block
next block →
recent activity
Analyzing
Block #96,146,799
10 transactions · 10 stateful · 2026-08-15 07:43:10 UTC
Parallelism
70
/100
Blocked
30
%
Avg conflicts / tx
0.4
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,146,799
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5acec890
#2
0x5acec890
#3
0x5acec890
#4
execFwdPositionOpsV2
· blocks 2
#6
0x94defb17
· blocks 1
#9
setData
#5
execFwdPositionOpsV2
· blocks 1
#7
0x94defb17
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w0
7
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe3c082c7…f032
0x34b655…2a6f
6 touches
3 conflicts
0xe02da8c7…dcd5
0x968279…9342
4 touches
1 conflict
0x0c3ac5cc…31d9
0x968279…9342
4 touches
1 conflict
0x0c3ac5cc…31da
0x968279…9342
4 touches
1 conflict
0x0c3ac5cc…31dd
0x968279…9342
4 touches
1 conflict
0x0c3ac5cc…31de
0x968279…9342
4 touches
1 conflict
0x0c3ac5cc…31df
0x968279…9342
4 touches
1 conflict
0xe02da8c7…dcd2
0x968279…9342
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
3 conflicts on slot
0xe3c082c74d…15f032
Audit this contract →
← previous block
·
next block →
recent activity