pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#104,333,954
← previous block
next block →
recent activity
Analyzing
Block #104,333,954
9 transactions · 8 stateful · 2026-09-13 01:31:03 UTC
Parallelism
67
/100
Blocked
38
%
Avg conflicts / tx
0.44
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#104,333,954
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
execOrders
#3
execFwdPositionOpsV2
· blocks 1
#5
transferWithAuthorization
· blocks 2
#8
setData
#4
execOrders
#6
transferWithAuthorization
· blocks 1
#7
transferWithAuthorization
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w0
6
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0xfeb7f784…7e2a
0x34b655…2a6f
4 touches
1 conflict
0xe2c4da1c…0e41
0x34b655…2a6f
4 touches
1 conflict
0x0b5b5bd5…565b
0x34b655…2a6f
2 touches
0 conflicts
0x0f3152e8…f181
0x34b655…2a6f
2 touches
0 conflicts
0x2adcce1b…3a0d
0x34b655…2a6f
2 touches
0 conflicts
0x4f4bdabd…ffba
0x34b655…2a6f
2 touches
0 conflicts
0x5666db7d…5dc4
0x34b655…2a6f
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)
3 conflicts on slot
0xd17580f913…78ece1
Audit this contract →
← previous block
·
next block →
recent activity