pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,445,844
← previous block
next block →
recent activity
Analyzing
Block #102,445,844
19 transactions · 18 stateful · 2026-09-06 10:31:07 UTC
Parallelism
89
/100
Blocked
17
%
Avg conflicts / tx
0.16
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,445,844
· 19 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
execOrders
#3
0x5acec890
#4
0x5acec890
#5
0x5acec890
· blocks 1
#6
updateDataFeedsValuesPartial
#7
0x59558d29
· blocks 1
#9
setData
#10
execFwdPositionOpsV2
#11
0xed82b078
#12
execFwdPositionOpsV2
#13
execFwdPositionOpsV2
#14
0xed82b078
#15
0x6a9d40ee
· blocks 1
#17
withdraw
#8
0x59558d29
#16
0x6a9d40ee
#18
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w0
8
w1
15
w0
16
w1
18
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xf5d6049c…8bc5
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001b
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002b
0x1b6862…e19c
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:
0x80c74517…647210
1 conflict on slot
0x0000000000…00004b
Audit this contract →
← previous block
·
next block →
recent activity