pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,011,531
← previous block
next block →
recent activity
Analyzing
Block #102,011,531
14 transactions · 12 stateful · 2026-09-04 21:50:25 UTC
Parallelism
86
/100
Blocked
25
%
Avg conflicts / tx
0.21
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,011,531
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#2
0x00691456
#3
swap
#5
main_all
#6
execOrders
#7
0xab083028
#8
0x3e2e8792
#9
updateDataFeedsValuesPartial
#11
setData
#12
execFwdPositionOpsV2
· blocks 1
#4
main_all
#10
0x0c7abd22
#13
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
10
w1
12
w0
13
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x4c770fe0…b972
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x714a26…182d
4 touches
1 conflict
0x00000000…0001
0x714a26…182d
4 touches
1 conflict
0x00000000…0003
0x714a26…182d
4 touches
1 conflict
0x392a02b5…0019
0x81a224…7777
4 touches
1 conflict
0xb6e6f2b2…9d90
0xd32edf…ff58
3 touches
1 conflict
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
0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block
·
next block →
recent activity