pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,439,722
← previous block
next block →
recent activity
Analyzing
Block #100,439,722
10 transactions · 10 stateful · 2026-08-30 09:57:18 UTC
Parallelism
50
/100
Blocked
40
%
Avg conflicts / tx
1
Longest chain
5
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,439,722
· 10 txs across 5 waves · depth 5
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
#0
syscallReward
#1
updatePrices
#2
0xab083028
#3
execute
#4
0x59558d29
#5
transferWithAuthorization
· blocks 4
#6
transferWithAuthorization
· blocks 3
#7
transferWithAuthorization
· blocks 2
#8
transferWithAuthorization
· blocks 1
#9
transferWithAuthorization
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
7
w2
8
w3
9
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
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x34d5be38…1100
0x6f7e11…3d7e
2 touches
0 conflicts
0x21d50a18…09fc
0x754704…b603
2 touches
0 conflicts
0x2b6e9ab7…3f41
0x754704…b603
2 touches
0 conflicts
0x3ee03352…3d87
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