pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,991,454
← previous block
next block →
recent activity
Analyzing
Block #99,991,454
10 transactions · 8 stateful · 2026-08-28 20:17:21 UTC
Parallelism
70
/100
Blocked
25
%
Avg conflicts / tx
0.4
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,991,454
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#3
execute_route
#4
execute_route
#5
0xa96df62f
#6
updatePrices
· blocks 1
#7
0x5acec890
#9
setData
#2
0x0c7abd22
· blocks 1
#8
0x41a8f47c
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
6
w0
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x99ac4675…5b23
0x065c9d…c394
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x17a7f697…dcb3
0x1b6862…e19c
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x3858cbfa…3549
0xd32edf…ff58
3 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)
3 conflicts on slot
0xa1087a5ca6…0a66c4
Audit this contract →
← previous block
·
next block →
recent activity