pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,527,224
← previous block
next block →
recent activity
Analyzing
Block #102,527,224
10 transactions · 9 stateful · 2026-09-06 17:23:53 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,527,224
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrders
#2
0x59558d29
#3
poke
#4
setData
#5
execFwdPositionOpsV2
· blocks 2
#8
0xed82b078
#9
0x6a9da1ac
#6
execFwdPositionOpsV2
· blocks 1
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x2014e4bd…c10b
0x34b655…2a6f
6 touches
3 conflicts
0xdf00e2d7…5ada
0x34b655…2a6f
6 touches
3 conflicts
0x6c28863e…840e
0x34b655…2a6f
6 touches
3 conflicts
0x4188cc5f…2d2e
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0x9bf17d13…7d07
0x34b655…2a6f
5 touches
3 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
0x0000000000…0000c9
Audit this contract →
← previous block
·
next block →
recent activity