pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,605,747
← previous block
next block →
recent activity
Analyzing
Block #98,605,747
7 transactions · 7 stateful · 2026-08-23 23:26:44 UTC
Parallelism
57
/100
Blocked
29
%
Avg conflicts / tx
0.43
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,605,747
· 7 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xa96df62f
#2
execFwdPositionOpsV2
#3
0x29eed2d3
· blocks 2
#6
0x6a8b822c
#4
0x29eed2d3
· blocks 1
#5
0x29eed2d3
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5311f864…0984
0x754704…b603
6 touches
3 conflicts
0xc111023f…a669
0x928dc8…8207
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0de7749d…5bef
0x34b655…2a6f
2 touches
0 conflicts
0x0f82d0e0…cffe
0x34b655…2a6f
2 touches
0 conflicts
0x103e4080…0d3a
0x34b655…2a6f
2 touches
0 conflicts
0x12be1917…03db
0x34b655…2a6f
2 touches
0 conflicts
0x12be8c6b…08c0
0x34b655…2a6f
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:
USDC (USDC)
3 conflicts on slot
0x5311f86450…380984
Audit this contract →
← previous block
·
next block →
recent activity