pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,701,876
← previous block
next block →
recent activity
Analyzing
Block #89,701,876
9 transactions · 9 stateful · 2026-07-23 18:23:42 UTC
Parallelism
78
/100
Blocked
22
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,701,876
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 1
#2
execFwdPositionOps
#3
0x3f5c179b
#4
0xce1e7030
· blocks 1
#7
setData
#8
execOrders
#5
0xce1e7030
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w0
5
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xddc22bc2…7f7a
0x754704…b603
4 touches
1 conflict
0x062b2598…4e28
0x43cf54…7777
4 touches
1 conflict
0x0dbf9688…c6cf
0x43cf54…7777
4 touches
1 conflict
0x00000000…0000
0x4b6ce4…7f37
4 touches
1 conflict
0x00000000…0002
0x4b6ce4…7f37
4 touches
1 conflict
0x00000000…0003
0x4b6ce4…7f37
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x6faa97ed…6c78
0x065c9d…c394
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:
USDC (USDC)
1 conflict on slot
0xddc22bc2be…bf7f7a
Audit this contract →
← previous block
·
next block →
recent activity