pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,205,122
← previous block
next block →
recent activity
Analyzing
Block #102,205,122
13 transactions · 13 stateful · 2026-09-05 14:11:42 UTC
Parallelism
77
/100
Blocked
15
%
Avg conflicts / tx
0.15
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,205,122
· 13 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
approve
· blocks 1
#3
matchOrders
#4
execOrders
#5
0xab083028
#6
0xab083028
#7
0x5acec890
#8
0x59558d29
#10
setData
#11
execFwdPositionOpsV2
#12
execOrders
#2
swap
· blocks 1
#9
settle
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b0621ee…3c2c
0x284f45…7777
4 touches
1 conflict
0xdf409966…6b16
0x3bd359…433a
4 touches
1 conflict
0x4eb758b8…b13b
0x3bd359…433a
4 touches
1 conflict
0xa164d951…1534
0xe1c8b7…3022
4 touches
1 conflict
0x00000000…0004
0x7aed55…0617
4 touches
1 conflict
0xd868fb65…3b4a
0xe1c8b7…3022
3 touches
1 conflict
0x816820f6…b254
0x284f45…7777
2 touches
1 conflict
0xa165a1e5…67be
0x754704…b603
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:
0x284f45fa…de7777
1 conflict on slot
0x5b0621ee5a…623c2c
Audit this contract →
← previous block
·
next block →
recent activity