pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,737,464
← previous block
next block →
recent activity
Analyzing
Block #97,737,464
11 transactions · 10 stateful · 2026-08-20 22:02:40 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,737,464
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x7b84f330
· blocks 1
#2
0x6ad2e98b
#3
execFwdPositionOpsV2
#4
updatePosition
#5
0x94defb17
#6
0xed82b078
#7
forward
#8
execFwdPositionOpsV2
#9
setData
#10
0x7b84f330
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x37e1be01…6f19
0x54cd53…9e7d
2 touches
0 conflicts
0xa27fa22d…7dca
0x54cd53…9e7d
2 touches
0 conflicts
0xd1a0adf6…6e55
0x54cd53…9e7d
2 touches
0 conflicts
0x02f52cb1…a99b
0x6657d1…8ccc
2 touches
0 conflicts
0x08532438…76fd
0x6657d1…8ccc
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:
0xc1570aa1…7ac91b
1 conflict on slot
0x0000000000…000007
Audit this contract →
← previous block
·
next block →
recent activity