pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,263,030
← previous block
next block →
recent activity
Analyzing
Block #99,263,030
9 transactions · 8 stateful · 2026-08-26 06:56:47 UTC
Parallelism
44
/100
Blocked
50
%
Avg conflicts / tx
1.11
Longest chain
5
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,263,030
· 9 txs across 5 waves · depth 5
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
#0
syscallReward
#1
0xab8718…aaa3
#2
0x59558d29
#3
createProxy
#4
transferWithAuthorization
· blocks 4
#5
transferWithAuthorization
· blocks 3
#6
transferWithAuthorization
· blocks 2
#7
transferWithAuthorization
· blocks 1
#8
transferWithAuthorization
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w2
7
w3
8
w4
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd17580f9…ece1
0x754704…b603
10 touches
10 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x4abe2dfd…96ae
0x754704…b603
2 touches
0 conflicts
0x7e955898…4ded
0x754704…b603
2 touches
0 conflicts
0x898a39ab…a12c
0x754704…b603
2 touches
0 conflicts
0xda807e3b…22e8
0x754704…b603
2 touches
0 conflicts
0xdc2747fa…2f24
0x754704…b603
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)
10 conflicts on slot
0xd17580f913…78ece1
Audit this contract →
← previous block
·
next block →
recent activity