pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,607,701
← previous block
next block →
recent activity
Analyzing
Block #100,607,701
38 transactions · 29 stateful · 2026-08-31 00:02:26 UTC
Parallelism
84
/100
Blocked
38
%
Avg conflicts / tx
0.42
Longest chain
6
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,607,701
· 38 txs across 6 waves · depth 6
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
#0
syscallReward
#1
0x1ada0a83
#2
execute
#3
0x50a0b275
#4
0xab083028
· blocks 1
#5
0x6a94c50a
· blocks 1
#6
0x6a94c509
#7
updatePrices
#8
execOrders
#9
updateDataFeedsValuesPartial
#10
0x0c7abd22
#11
execPerpOps
#12
execOrders
· blocks 2
#13
execOrders
· blocks 1
#14
execOrders
#15
execPerpOps
· blocks 1
#17
0xe3a3c9cc
#18
0x41a8f47c
#19
0x62be7533
#20
execFwdPositionOpsV2
· blocks 1
#22
updatePriceFeedsIfNecessary
#23
0x3f5c179b
· blocks 1
#26
0x3f5c179b
· blocks 1
#28
0xed82b078
#30
topUp
#32
setData
#33
0x32366535
#16
execPerpOps
#21
execFwdPositionOpsV2
· blocks 2
#25
0x3f5c179b
#27
0xed82b078
#31
0x6a94c50a
#34
0xc7068c7b
#24
execFwdPositionOpsV2
· blocks 2
#29
execFwdPositionOpsV2
#35
execOrders
· blocks 2
#36
execOrders
· blocks 1
#37
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w0
12
w0
13
w0
15
w0
16
w1
20
w0
21
w1
23
w0
24
w2
25
w1
26
w0
27
w1
29
w3
31
w1
34
w1
35
w3
36
w4
37
w5
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x5d1ac445…5233
0x34b655…2a6f
4 touches
1 conflict
0x6f6fc26c…3e34
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4a1
0x34b655…2a6f
4 touches
1 conflict
0x9f77282b…47a2
0x34b655…2a6f
4 touches
1 conflict
0xbae5b1aa…2722
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 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
3 conflicts on slot
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity