pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,253,930
← previous block
next block →
recent activity
Analyzing
Block #102,253,930
13 transactions · 13 stateful · 2026-09-05 18:18:54 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,253,930
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
executePacked
#2
execOrders
#3
0x8263f5d9
#4
0x0c7abd22
#5
0x5acec890
#6
0x5acec890
#7
0x59558d29
#8
setData
#9
execFwdPositionOpsV2
· blocks 1
#10
0x6a9c5d12
#11
execOrders
· blocks 1
#12
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
11
w0
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x839c0c71…bada
0x34b655…2a6f
4 touches
1 conflict
0x899a95b3…c38a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x12530975…a089
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0001
0x453805…c7fd
2 touches
0 conflicts
0x00000000…0002
0x453805…c7fd
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
0x839c0c712a…78bada
Audit this contract →
← previous block
·
next block →
recent activity