pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,137,515
← previous block
next block →
recent activity
Analyzing
Block #102,137,515
11 transactions · 11 stateful · 2026-09-05 08:28:57 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,137,515
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
execOrders
#3
0x0c7abd22
· blocks 1
#4
0x5acec890
#5
executeBatch
#6
setData
#7
execFwdPositionOpsV2
· blocks 1
#9
0x6a9bd2cc
#10
execOrders
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x502b3ee1…7f7c
0x34b655…2a6f
4 touches
1 conflict
0x1db5837f…1264
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x16efd770…2159
0x34b655…2a6f
4 touches
1 conflict
0x1e9a3fc4…c4e1
0x34b655…2a6f
2 touches
0 conflicts
0x2d2b5c10…fc6d
0x34b655…2a6f
2 touches
0 conflicts
0x31d88d27…7617
0x34b655…2a6f
2 touches
0 conflicts
0x62bb20db…431e
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
0x502b3ee1e6…227f7c
Audit this contract →
← previous block
·
next block →
recent activity