pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,205,655
← previous block
next block →
recent activity
Analyzing
Block #102,205,655
10 transactions · 10 stateful · 2026-09-05 14:14:25 UTC
Parallelism
80
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,205,655
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39ecce49
· blocks 1
#2
updatePrices
#4
permit2TransferAndMulticall
#5
setData
#6
execFwdPositionOpsV2
· blocks 1
#7
0xed82b078
#8
execFwdPositionOpsV2
#3
permit2TransferAndMulticall
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
6
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4eb758b8…b13b
0x3bd359…433a
4 touches
1 conflict
0x5b0621ee…3c2c
0x284f45…7777
4 touches
1 conflict
0x00000000…0004
0x7aed55…0617
4 touches
1 conflict
0xdf409966…6b16
0x3bd359…433a
4 touches
1 conflict
0xfd4e632c…e14c
0x34b655…2a6f
4 touches
1 conflict
0xa164d951…1534
0xe1c8b7…3022
4 touches
1 conflict
0xd868fb65…3b4a
0xe1c8b7…3022
4 touches
1 conflict
0x44ed742f…63f5
0x3bd359…433a
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:
Wrapped MON (WMON)
1 conflict on slot
0x4eb758b864…6cb13b
Audit this contract →
← previous block
·
next block →
recent activity