pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,155,387
← previous block
next block →
recent activity
Analyzing
Block #100,155,387
9 transactions · 8 stateful · 2026-08-29 10:02:47 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,155,387
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
0x6ad2e98b
#3
execOrders
· blocks 2
#4
0x3f5c179b
#7
setData
#8
exactInputSingle
#5
execFwdPositionOpsV2
· blocks 1
#6
redeemDelegations
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00f6a8a7…0e6e
0x34b655…2a6f
6 touches
3 conflicts
0xc8328065…611a
0x34b655…2a6f
6 touches
3 conflicts
0xc87e767e…4bba
0x34b655…2a6f
4 touches
1 conflict
0xcb9d2fcb…c9cd
0x34b655…2a6f
4 touches
1 conflict
0x206f4379…e08a
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
2 touches
0 conflicts
0xa169711f…c7f3
0x34b655…2a6f
2 touches
0 conflicts
0xd1b79aeb…a0d2
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
3 conflicts on slot
0x00f6a8a766…070e6e
Audit this contract →
← previous block
·
next block →
recent activity