pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,872,410
← previous block
next block →
recent activity
Analyzing
Block #89,872,410
7 transactions · 6 stateful · 2026-07-24 08:44:05 UTC
Parallelism
57
/100
Blocked
33
%
Avg conflicts / tx
0.43
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,872,410
· 7 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xce1e7030
· blocks 2
#4
execFwdPositionOps
#5
0xd708c5d8
#6
setData
#2
0xce1e7030
· blocks 1
#3
0xce1e7030
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xddc22bc2…7f7a
0x754704…b603
6 touches
3 conflicts
0x4c770fe0…b972
0x3bd359…433a
6 touches
3 conflicts
0x392a02b5…0019
0x81a224…7777
6 touches
3 conflicts
0x6882c020…1910
0x81a224…7777
6 touches
3 conflicts
0x31d03340…6bc2
0xe7a4f9…4b2d
6 touches
3 conflicts
0x8592f52d…c27f
0xe7a4f9…4b2d
6 touches
3 conflicts
0x00000000…0000
0x714a26…182d
6 touches
3 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
0xa1087a5ca6…0a66c4
Audit this contract →
← previous block
·
next block →
recent activity