pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,248,516
← previous block
next block →
recent activity
Analyzing
Block #102,248,516
8 transactions · 8 stateful · 2026-09-05 17:51:29 UTC
Parallelism
38
/100
Blocked
50
%
Avg conflicts / tx
1.25
Longest chain
5
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,248,516
· 8 txs across 5 waves · depth 5
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
#0
syscallReward
#1
0x59558d29
#2
transferWithAuthorization
· blocks 4
#7
setData
#3
transferWithAuthorization
· blocks 3
#4
transferWithAuthorization
· blocks 2
#5
transferWithAuthorization
· blocks 1
#6
transferWithAuthorization
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
5
w3
6
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
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x2a34fb2e…f13e
0x754704…b603
2 touches
0 conflicts
0x32d0ab82…ed34
0x754704…b603
2 touches
0 conflicts
0x4fd07804…8522
0x754704…b603
2 touches
0 conflicts
0x8982c726…e24a
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