pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,580,947
← previous block
next block →
recent activity
Analyzing
Block #98,580,947
5 transactions · 5 stateful · 2026-08-23 21:17:24 UTC
Parallelism
60
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,580,947
· 5 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x94defb17
· blocks 1
#3
execFwdPositionOpsV2
#4
0x6a8b63dc
#2
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdea6084b…e140
0x8964d7…10f8
4 touches
1 conflict
0x2a07e64e…fe77
0x754704…b603
4 touches
1 conflict
0x00000000…0008
0x8964d7…10f8
4 touches
1 conflict
0x8cdd5761…d3f1
0x8964d7…10f8
4 touches
1 conflict
0x8cdd5761…d3f2
0x8964d7…10f8
4 touches
1 conflict
0x8cdd5761…d3f4
0x8964d7…10f8
4 touches
1 conflict
0xdea6084b…e13a
0x8964d7…10f8
4 touches
1 conflict
0xdea6084b…e13b
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
0xdea6084b9e…afe140
Audit this contract →
← previous block
·
next block →
recent activity