pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,558,363
← previous block
next block →
recent activity
Analyzing
Block #97,558,363
11 transactions · 10 stateful · 2026-08-20 06:49:38 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,558,363
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
exec
#2
0xab083028
#3
updateDataFeedsValuesPartial
#4
0x5acec890
· blocks 1
#6
0x94defb17
· blocks 1
#8
setData
#9
swapExactTokensForTokens
#10
0x59558d29
#5
0x928e4afa
#7
0x94defb17
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
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4a214993…74f7
0x8964d7…10f8
4 touches
1 conflict
0x4a214993…74f8
0x8964d7…10f8
4 touches
1 conflict
0x4a214993…74fa
0x8964d7…10f8
4 touches
1 conflict
0xea44e1df…ad83
0x8964d7…10f8
4 touches
1 conflict
0xea44e1df…ad84
0x8964d7…10f8
4 touches
1 conflict
0xea44e1df…ad87
0x8964d7…10f8
4 touches
1 conflict
0xea44e1df…ad88
0x8964d7…10f8
4 touches
1 conflict
0xea44e1df…ad8a
0x8964d7…10f8
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:
0x8964d7c9…5b10f8
1 conflict on slot
0x4a214993bd…8774f7
Audit this contract →
← previous block
·
next block →
recent activity