pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,107,144
← previous block
next block →
recent activity
Analyzing
Block #102,107,144
14 transactions · 14 stateful · 2026-09-05 05:55:04 UTC
Parallelism
86
/100
Blocked
7
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,107,144
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
exec
#2
0xab083028
#3
0xab083028
#4
0x0c7abd22
· blocks 1
#5
0x5acec890
#6
0x5acec890
· blocks 1
#8
0x928e4afa
#9
0x59558d29
#10
setData
#11
execFwdPositionOpsV2
#12
execFwdPositionOpsV2
#13
transfer
#7
0x5acec890
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70e677f5…e3bd
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xb83627b6…f135
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0004
0x031cc3…255f
2 touches
0 conflicts
0x00000000…000c
0x031cc3…255f
2 touches
0 conflicts
0x00000000…0008
0x0a6325…bcfc
2 touches
0 conflicts
0x00000000…0009
0x0a6325…bcfc
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
0x70e677f5c0…90e3bd
Audit this contract →
← previous block
·
next block →
recent activity