pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#106,215,219
← previous block
next block →
recent activity
Analyzing
Block #106,215,219
8 transactions · 7 stateful · 2026-09-19 15:40:13 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#106,215,219
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updatePrices
#3
0x5acec890
#4
sweepNative
#5
execFwdPositionOpsV2
· blocks 1
#7
transferWithAuthorization
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac0b4a08…faae
0x34b655…2a6f
4 touches
1 conflict
0x85eb1316…bb9e
0x34b655…2a6f
4 touches
1 conflict
0xb7b1e3c8…6fe0
0x34b655…2a6f
4 touches
1 conflict
0x12503a94…ffdb
0x34b655…2a6f
4 touches
1 conflict
0x0087ca84…0b18
0x34b655…2a6f
2 touches
0 conflicts
0x051f2702…ea73
0x34b655…2a6f
2 touches
0 conflicts
0x07c2e48b…3c16
0x34b655…2a6f
2 touches
0 conflicts
0x108dc469…3b33
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:
Perpl
1 conflict on slot
0xac0b4a0805…e6faae
Audit this contract →
← previous block
·
next block →
recent activity