pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,854,190
← previous block
next block →
recent activity
Analyzing
Block #101,854,190
11 transactions · 11 stateful · 2026-09-04 08:33:54 UTC
Parallelism
64
/100
Blocked
36
%
Avg conflicts / tx
0.64
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,854,190
· 11 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x0c7abd22
· blocks 3
#3
0x3e2e8792
· blocks 1
#6
setData
#7
forward
#9
execFwdPositionOpsV2
#10
execFwdPositionOpsV2
#2
0xd60faa87
· blocks 2
#8
execFwdPositionOpsV2
#4
0x6c05cd2b
· blocks 1
#5
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
4
w2
5
w3
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa060b594…669d
0x754704…b603
8 touches
6 conflicts
0x00000000…0000
0x834d94…8555
8 touches
6 conflicts
0x00000000…0004
0x834d94…8555
8 touches
6 conflicts
0x0ef74796…cd18
0x0a3323…0a3c
8 touches
6 conflicts
0x00000000…0003
0x834d94…8555
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0xd53220ed…473b
0x1b6862…e19c
4 touches
1 conflict
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
0xa060b59478…f7669d
Audit this contract →
← previous block
·
next block →
recent activity