pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,476,252
← previous block
next block →
recent activity
Analyzing
Block #102,476,252
9 transactions · 9 stateful · 2026-09-06 13:05:14 UTC
Parallelism
56
/100
Blocked
44
%
Avg conflicts / tx
0.78
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,476,252
· 9 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
settle
· blocks 1
#2
transferWithAuthorization
· blocks 3
#7
0x6a9d650d
#8
execOrders
#3
transferWithAuthorization
· blocks 2
#6
handleOps
#4
transferWithAuthorization
· blocks 1
#5
transferWithAuthorization
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
3
w1
4
w2
5
w3
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd17580f9…ece1
0x754704…b603
8 touches
6 conflicts
0x4eb758b8…b13b
0x3bd359…433a
4 touches
1 conflict
0xa164d951…1534
0xe1c8b7…3022
4 touches
1 conflict
0x78a08107…b21a
0x3bd359…433a
2 touches
0 conflicts
0xb6490b9d…8d82
0x3bd359…433a
2 touches
0 conflicts
0xe351e207…b3ca
0x3bd359…433a
2 touches
0 conflicts
0xdbf411ab…61b8
0x687f91…f6f4
2 touches
0 conflicts
0x2d749715…b272
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)
6 conflicts on slot
0xd17580f913…78ece1
Audit this contract →
← previous block
·
next block →
recent activity